RE: Gen-ART review of draft-ietf-oauth-v2-bearer-15.txt

Thanks for your useful feedback, Alexey. Below, I'll respond to each of your comments. I've also added the OAuth working group to the thread, so they are aware of them as well and can participate in the discussion. About your first issue with the WWW-Authenticate ABNF, I am already working wi

Re: secdir review of draft-nottingham-http-new-status-03

I haven't heard any further response. After a reminder from a Security AD, I took another look at the spec. E.g., the current Security Considerations for 428: > The 428 status code is optional; clients cannot rely upon its use to prevent > "lost update" conflicts. Like many of the status codes

Gen-ART review of draft-ietf-oauth-v2-bearer-15.txt

I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at . Please resolve these comments along with any other Last Call comments you may receive. Document: draft-ietf-oauth-v2-bearer-15.txt Re

Re: Last Call: (The RPKI/Router Protocol) to Proposed Standard

Hello, I received a comment about the following comment I made previously ( http://www.ietf.org/mail-archive/web/ietf/current/msg71561.html ): "It is somewhat unfortunate that Huawei did not get the opportunity to send Last Call comments as Cisco Systems and Juniper Networks Inc did." Th

Gen-ART LC review of draft-ietf-dnsext-ecdsa-04

I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at . Please resolve these comments along with any other Last Call comments you may receive. Document: draft-ietf-dnsext-ecdsa-04 Reviewer:

Re: Commentary about IETF protocols which do not provide IP protection in their use.

On Sun, Jan 29, 2012 at 6:27 PM, todd glassey wrote: > Today virtually no IETF protocols take into account US or any other > countries copyright laws with regard to Internet based content. Content > like domain names, DNS events, and BGP4 routes are also in addition to > the obvious publication ev

Commentary about IETF protocols which do not provide IP protection in their use.

Today virtually no IETF protocols take into account US or any other countries copyright laws with regard to Internet based content. Content like domain names, DNS events, and BGP4 routes are also in addition to the obvious publication events like a websites content, are in fact also IP impinged. S