The problem with option 1 is that it amounts to the IESG making a change to a document that the authors don't want made and that doesn't have working group consensus, or else you open up the document. I think that right now we are not really in danger of widespread implementation of homenet, although I would be overjoyed to hear you tell me that I am wrong (Dan).
So I think the more expedient and kinder route to go is to just do a follow-on document for now, and wrap the ultimate change, which I hope will be to allocate .homenet as the default, into the next genuine rev of the document. This is less likely to demotivate the authors and the working group by compressing the update schedule for the document, or by forcing them/us to do a rev with only one change. This is _not_ to say that your point (Dan) was wrong. Just that I don't think your proposed approach is necessary. We still do need to consider implementors, and that's why I think that doing two updates and _then_ a 7788bis is better than just waiting until 7788bis. However, if we are going to have a big fight over the followon-document that allocates a special-use TLN for homenets, that might change my opinion. On Thu, Jul 21, 2016 at 8:56 AM, Pierre Pfister <[email protected]> wrote: > Hello Dan, > > > I did not agree with any of the four choices offered by the chairs to > the WG for the resolution of the RFC 7788 / .home issue. > [...] > > > > I think the cleanest, simplest thing we can do *for the implementers* is > to publish a new RFC that *obsoletes* RFC 7788. We can then promote the > new RFC as the definitive standard for HNCP. RFC 7788 can get a big > "Obsolete" warning in the places we publish it - and documentation and > other new RFCs can reference the new RFC. > > > > If my memory is correct, what you describe was actually choice #1, which > got little humming in the room compared to 3 and 4 (and 5...). > > Cheers, > > - Pierre > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet >
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
