Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard]

2009-10-22 Thread Andrew Newton
On Oct 16, 2009, at 1:09 PM, Ted Hardie wrote: There was not many opaque URI defined in standard track since RFC 3986, but the IRIS URI (RFC 3981 section 7.1) looks like an opaque URI that reuse components from RFC 2396 and RFC 2732. Anyway, I can copy and rename the definitions that I

Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard]

2009-10-22 Thread Marc Petit-Huguenin
Hi Andrew, Andrew Newton wrote: On Oct 16, 2009, at 1:09 PM, Ted Hardie wrote: There was not many opaque URI defined in standard track since RFC 3986, but the IRIS URI (RFC 3981 section 7.1) looks like an opaque URI that reuse components from RFC 2396 and RFC 2732. Anyway, I can copy

Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard]

2009-10-22 Thread Andrew Newton
On Oct 22, 2009, at 3:05 PM, Marc Petit-Huguenin wrote: ... With regard to complexity, that is most likely in the eye of the beholder. I would think this is more complex than other uses of S-NAPTR. I don't know how one goes about judging these sort of things. Perhaps it would be helpful

Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt

2009-10-22 Thread Sam Hartman
Jari == Jari Arkko jari.ar...@piuha.net writes: Jari Dave, An accounting assessment of community views, justifying claims of rough consensus, is the usual approach towards resolving this kind of disparity. Jari That sounds like a fine plan. We got most input during the

Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard]

2009-10-22 Thread Marc Petit-Huguenin
Andrew Newton wrote: On Oct 22, 2009, at 3:05 PM, Marc Petit-Huguenin wrote: ... With regard to complexity, that is most likely in the eye of the beholder. I would think this is more complex than other uses of S-NAPTR. I don't know how one goes about judging these sort of things.

Re: Last Call: draft-gennai-smime-cnipa-pec (Certified Electronic Mail) to Proposed Standard

2009-10-22 Thread SM
At 12:57 13-10-2009, The IESG wrote: The IESG has received a request from an individual submitter to consider the following document: - 'Certified Electronic Mail ' draft-gennai-smime-cnipa-pec-05.txt as a Proposed Standard The IESG plans to make a decision in the next few weeks, and

Weekly posting summary for ietf@ietf.org

2009-10-22 Thread Thomas Narten
Total of 35 messages in the last 7 days. script run at: Fri Oct 23 00:53:01 EDT 2009 Messages | Bytes| Who +--++--+ 11.43% |4 | 21.23% |67869 | bernard_ab...@hotmail.com 14.29% |5 | 8.87% |28358 |

Protocol Action: 'Node behavior upon originating and receiving Resource ReserVation Protocol (RSVP) Path Error message' to BCP

2009-10-22 Thread The IESG
The IESG has approved the following document: - 'Node behavior upon originating and receiving Resource ReserVation Protocol (RSVP) Path Error message ' draft-ietf-mpls-3209-patherr-06.txt as a BCP This document is the product of the Multiprotocol Label Switching Working Group. The

RFC 5693 on Application-Layer Traffic Optimization (ALTO) Problem Statement

2009-10-22 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 5693 Title: Application-Layer Traffic Optimization (ALTO) Problem Statement Author: J. Seedorf, E. Burger Status: Informational Date:

RFC 5709 on OSPFv2 HMAC-SHA Cryptographic Authentication

2009-10-22 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 5709 Title: OSPFv2 HMAC-SHA Cryptographic Authentication Author: M. Bhatia, V. Manral, M. Fanto, R. White, M. Barnes, T. Li,