Re: [regext] Secdir telechat review of draft-ietf-regext-bundling-registration-11

2019-10-13 Thread John C Klensin
Sorry... Addendum to the technical comment quoted below: The document uses the term "variant" extensively, but does not define it either. That term seems essential to what is going on in this document. It des not appear in RFC 8499 (which is not cited in any event). The term was introduced into

Re: [regext] Secdir telechat review of draft-ietf-regext-bundling-registration-11

2019-10-13 Thread John C Klensin
--On Sunday, October 13, 2019 16:25 +0200 Barry Leiba wrote: >> The Abstract ans Section 1 say: "This is a non-standard >> proprietary extension." I understand that this is not a >> standards track document, so the "non-standard" part makes >> sense. However, what is the point of publishing a

Re: [regext] Secdir telechat review of draft-ietf-regext-bundling-registration-11

2019-10-13 Thread Barry Leiba
Works for me: I had suggested “proprietary”, so I will now unsuggest it. Authors, sorry about that: please remove that word in both places the next time you make a revision. Thanks. Barry On Sun, Oct 13, 2019 at 1:29 PM Paul Hoffman wrote: > On 13 Oct 2019, at 7:25, Barry Leiba wrote: > > >> T

Re: [regext] Secdir telechat review of draft-ietf-regext-bundling-registration-11

2019-10-13 Thread Paul Hoffman
On 13 Oct 2019, at 7:25, Barry Leiba wrote: The Abstract ans Section 1 say: "This is a non-standard proprietary extension." I understand that this is not a standards track document, so the "non-standard" part makes sense. However, what is the point of publishing a "proprietary" extension as a

Re: [regext] Secdir telechat review of draft-ietf-regext-bundling-registration-11

2019-10-13 Thread Barry Leiba
> The Abstract ans Section 1 say: "This is a non-standard proprietary > extension." I understand that this is not a standards track document, so > the "non-standard" part makes sense. However, what is the point of > publishing a "proprietary" extension as an RFC. I would hope that > interoperable

Re: [regext] Secdir telechat review of draft-ietf-regext-bundling-registration-11

2019-10-13 Thread Jiankang Yao
> -原始邮件- > 发件人: "Russ Housley via Datatracker" > 发送时间: 2019-10-10 23:02:57 (星期四) > 收件人: sec...@ietf.org > 抄送: draft-ietf-regext-bundling-registration@ietf.org, i...@ietf.org, > regext@ietf.org > 主题: Secdir telechat review of draft-ietf-regext-bundling-registration-11 > > Reviewer:

[regext] Secdir telechat review of draft-ietf-regext-bundling-registration-11

2019-10-10 Thread Russ Housley via Datatracker
Reviewer: Russ Housley Review result: Has Issues I reviewed this document as part of the Security Directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the Security Area Directors. Document authors, documen