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]/
[bcop] [Ext] IPv6 prefix delegation BCOP document v.7
- Previous message (by thread): [bcop] IPv6 prefix delegation BCOP document v.7
- Next message (by thread): [bcop] [Ext] IPv6 prefix delegation BCOP document v.7
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Paul Hoffman
paul.hoffman at icann.org
Mon Aug 21 16:40:35 CEST 2017
Greetings. The current version is OK, but it *might* be improved by saying that the advice in it contradicts various RFCs, and list those RFCs. Pro: - Readers of the BCOP who implement it will likely be told "you're doing it wrong, RFC AAAA and BBBB say to do it differently". Having your readers blindsided is bad. - Listing the differences shows that you thought about them, so no one can accuse you of not knowing about RFC AAAA and BBBB. Con: - You cause your readers to question your conclusions without being able to prove why your conclusions are better than those in the RFCs. This could lead your readers to think "I will wait until everyone agrees", which unfortunately translates into "I will make no changes to my configurations ever". So, yes, I'm ambivalent about this proposal. --Paul Hoffman
- Previous message (by thread): [bcop] IPv6 prefix delegation BCOP document v.7
- Next message (by thread): [bcop] [Ext] IPv6 prefix delegation BCOP document v.7
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ BCOP Archives ]