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] Last Call for publication of RIPE-501bis (reply by 20120426)
- Previous message (by thread): [ipv6-wg] Last Call for publication of RIPE-501bis (reply by 20120426)
- Next message (by thread): [ipv6-wg] New on RIPE Labs: Update on IPv6 Address Distribution
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Koch
pk at DENIC.DE
Wed May 2 08:36:59 CEST 2012
Shane, > > 1) I'm missing RFCs 2671 and 3226 ("Do support EDNS0 and do it right") > > in the list of requirements for mobile nodes. RFC 3596 is present, > > though. Usually the former are mandatory but I have no idea what > > special size considerations might have applied here. > > > > 2) Since all other devices are required to support EDNS0 with "large > > enough" payloads, the requirements list for CPEs should probably > > contain RFC 5625, so the CPEs do not get in the way of all those > > compliant gear on both sides. > > I think we need to publish the document without these changes. This is > a case where "the perfect is the enemy of the good"(*). believe it or not, that phrase even exists in German ;-) > Regarding future versions or an errata list... my own advice would be to > leave EDNS0 RFCs out of this document, since it is intended for IPv6 > recommendations not as a general "here are good things to have" > document. I admit I'm not sure where such a list would reside. :( I think consistency is key here, next time. -Peter
- Previous message (by thread): [ipv6-wg] Last Call for publication of RIPE-501bis (reply by 20120426)
- Next message (by thread): [ipv6-wg] New on RIPE Labs: Update on IPv6 Address Distribution
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]