Re: [newtrk] draft-ietf-newtrk-repurposing-isd-04.txt

[Brian E Carpenter <[e-mail]>]

...
> At this point, we seem to be headed back for yet another round of "is 
> there really a problem?" discussions. "There really is a problem", 
> probably not for everyone (it may be well-understood what SHIM6 is), but 
> for enough people to justify moving forward on ISDs, independent of 
> whether Newtrk does anything else or not.
> 
> We have been very conservative about RFC 3933 experiments involving the 
> standards track. Perhaps there are a small number of protocols that need 
> ISDs, and the rest do not. Given a choice between bootstrapping ISDs, 
> solving a real problem, and looking for broader applicability, and 
> another round of navel-gazing, should we consider moving forward with an 
> ISD experiment?

Well, shouldn't we discuss the docid draft first? My personal opinion is
that it looks like a fairly straightforward first step, and leaves the
way open for people to write ISD-like documents (or, if you prefer,
Applicability Statements on steroids) without even going outside
RFC 2026.

     Brian

.
newtrk resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html