This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/

[ipv6-wg] New version (or followup) of RIPE-501 document...

Previous message (by thread): [ipv6-wg] New version (or followup) of RIPE-501 document...
Next message (by thread): [ipv6-wg] New version (or followup) of RIPE-501 document...

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ole Troan ot at cisco.com
Sat Jun 18 20:11:47 CEST 2011

Jan,

>> My personal preference is variant 2. Less text is good I think.
> 
> Agree to some extent...
> 
> What does one RFC means to procurement people and how they check if CPE fits the requirements? In this case procurement guy needs to interpret all requirements from one RFC instead of the given list.
> 
> still not sure...

RFC6104 _is_ just that; a device profile to be used for procurement.
replicating this work in RIPE-501 seems redundant and more cause for confusion than help. we do after all have 3 of the IPv6 CPE profiles now. eRouter from CableLabs, TR-124i2 from BroadbandForum and RFC6104 from the IETF.

cheers,
Ole

Previous message (by thread): [ipv6-wg] New version (or followup) of RIPE-501 document...
Next message (by thread): [ipv6-wg] New version (or followup) of RIPE-501 document...

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]