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/[email protected]/

[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] v6day.ripe.net

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

Jan Zorz @ go6.si jan at go6.si
Fri Jun 17 17:10:01 CEST 2011

BTW, just to let you know, there is a Cisco position paper on RIPE-501 :)

http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6553/brief_c80-674464.html

We should probably address their comments, specially the one that talks 
about RFC sets:

"In option 1, RIPE-501 cherry-picks requirements from USGv6 and then 
adds its own without enough justification. We think that weakens the 
credibility of the document."

We got solid consensus on RFC sets and changes were not taken 
"out-of-the-blue".

I think we need to stress out this fact in the document.

Any suggestions?

/jan

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

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

[ ipv6-wg Archives ]