I have some concerns about 6.1 in terms of whether it could be interpreted as a
definite statement of direction that we'll be building a new protocol rather
than identifying one to modify for use here, which I think is in conflict with
section 5 of the problem statement.
I agree that cobbling together several protocols that weren't meant to be
integrated isn't necessarily a good solution when compared with a single
protocol, so I think this may be a wording problem in the current text, rather
than a philosophical disagreement, but it's worth confirming that before we
adopt this draft. If I'm right that it's just a wording issue, it may be as
simple as adding the same words from the problem statement:
"Whether such a protocol is built upon extending
existing mechanisms or requires a new mechanism requires further
investigation."
Otherwise I think it's in good shape.
Thanks,
Wes George
From: [email protected] [mailto:[email protected]] On Behalf Of Alia
Atlas
Sent: Wednesday, July 24, 2013 5:52 PM
To: [email protected]
Subject: [i2rs] Call for Adoption by WG: draft-atlas-i2rs-architecture-01 (ends
Aug 12)
Please review draft-atlas-i2rs-architecture-01 and comment on whether it should
be adopted by I2RS. Detailed technical conversation is also most welcome.
Authors: Are you aware of any IPR that applies to
draft-atlas-i2rs-architecture-01? Is so, has this IPR been disclosed in
compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more
details).
This WG call for adoption will complete on August 12.
Thanks,
Alia
________________________________
This E-mail and any of its attachments may contain Time Warner Cable
proprietary information, which is privileged, confidential, or subject to
copyright belonging to Time Warner Cable. This E-mail is intended solely for
the use of the individual or entity to which it is addressed. If you are not
the intended recipient of this E-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify the sender
immediately and permanently delete the original and any copy of this E-mail and
any printout.
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
