[ipv6-wg] "Requirements For IPv6 in ICT Equipment" comment

Yannis, hi.

On 1/17/11 4:09 PM, Dez wrote:
> actually, the requirements were mostly gathered from 
> http://tools.ietf.org/html/draft-ietf-v6ops-ipv6-cpe-router-07 
> (haven't checked the diff with the new version yet). I agree with 
> Marco and others about using the IETF doc as reference but I'm not 
> sure if there's much of a point in making a RIPE document that 
> basically points to the IETF draft.

Facing the crossroad here... We would like to make the doc as simple as 
possible and pointing to RFC is easiest way to do this. On the other 
hand, not only simple, RIPE-501bis needs to be usefull and can be used 
even by people that don't read RFCs.

>
>> Not sure yet, do we just point to Ole's draft (that is excellent 
>> imho) or do we write a list of mandatory RFCs that are 1:1 in sync 
>> with the draft and BBF paper (Ole is also editing that) and keep the 
>> list in sync if draft/RFC changes. This way tender initiator can just 
>> copy/paste RFCs and this way the job is easy.
>>
>
> that last proposal makes sense to me
The key question here is how stable that draft is and what would be 
syncing efforts like.

When looking from shape point of view, we have currently 4 sections of 
equipment, all of them says:

Mandatory:
... [list]

Optional:
... [list]

And 5th section would say Mandatory -> external RFC.

Hmm.

Cheers, Jan