On 7/10/15 9:06 AM, Suzanne Woolf wrote:
> Bill,
> 
> On Jul 10, 2015, at 9:38 AM, Olafur Gudmundsson <o...@ogud.com>
> wrote:
> 
>> Question: What sections of 2181 do you see the need to update?
> 
> This seems to be the critical question to your chairs and our AD as
> well.
> 
> If I understand it correctly, your proposed document roadmap has us
> putting eight documents through the process as standards-track RFCs
> with no change in substance from RFC 2181, so we can then put three
> more documents through the process with new content. This seems like
> a very process-heavy way to update 2181.

It does,

Also there are  4035, 2535, 4343, 4033, 4034, 5452   which update
respective portions of 2181 so breaking apart 2181 into individual
pieces from the outset means incorporating those updates (fine I guess)
but then you're operating on those drafts; or walking back those changes
which I doubt is your intent.

This is a foggy recollection but I'll recount it here, by way of
communicating my own thoughts.

When Bill asked me at nanog what I though of multiple 2181 changes. I
proffered the opinion that. given that 2181 is several topics (7 I
think) it would be best if each proposed update to a topic taken on in
2181 were to be a seperate draft so that could be discussed on their
invidual merits rather than as a package of changes to 2181. 4343 and
5452 I would treat as precident  for that.

that is not a call imho for splitting appart 2181 first and then
proposing changes. if I was interpreted at any time as proposing that
I'm sorry.

> It's also hard to commit to obsoleting 2181 in eight separate steps
> without seeing the proposed updated content will be, or knowing
> whether it will get to consensus.
> 
> Could you describe the substance of what you think needs to be
> changed? If the WG wants to do the work, we can manage the process
> machinery accordingly.
> 
> 
> thanks, Suzanne
> 
> 
> 
> 
> 
> _______________________________________________ DNSOP mailing list 
> DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
> 


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to