Re: Legality of IETF meetings in PRC. Was: Re: Request for community guidance on issue concerning a future meeting of the IETF
(Personal opinion) On Mon, 5 Oct 2009, Margaret Wasserman wrote: While I do think that the IAOC should be aware of the potential legal implications of where we hold our meetings, I wonder if we are treating China unfairly in this discussion... I agree. So-far, we have always assumed that discussions on crypto as well as writing, testing and using code during the meeting were legal in the country. And if they weren't, we'd assume that the local policy would not notice. China is not different in this respect. Perhaps this is something that we could expect our host to help us determine? The IAOC is in contact with the host about all the issues raised on the list (and then some more). Henk -- -- Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.xs4all.nl/~henku P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The NetherlandsThe NetherlandsMobile: +31.6.55861746 -- Belgium: an unsolvable problem, discussed in endless meetings, with no hope for a solution, where everybody still lives happily. ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
RE: Last Call: draft-ietf-l3vpn-e2e-rsvp-te-reqts (Requirements forsupporting Customer RSVP and RSVP-TE over a BGP/MPLS IP-VPN) toInformational RFC
Hi all. Just a few minor comments: - The I-D refers to the EXP field several times (pages 11, 13, 15, 17...) whereas it is now named Traffic Class, as per RFC 5462. - Section 5.8 tackles PCE, thus putting some requirements on the PCE WG: do we expect that they are endorsed tacitly? In this specific case, it is only specified as SHOULD, so impact is limited, but what is the status of this kind of draft defining requirements over multiple WGs? In case it be superset by draft-ietf-pce-vpn-req, a reference would be welcome. Thanks, Julien -Original Message- From: ietf-announce-boun...@ietf.org [mailto:ietf-announce-boun...@ietf.org] On Behalf Of The IESG The IESG has received a request from the Layer 3 Virtual Private Networks WG (l3vpn) to consider the following document: - 'Requirements for supporting Customer RSVP and RSVP-TE over a BGP/MPLS IP-VPN ' draft-ietf-l3vpn-e2e-rsvp-te-reqts-04.txt as an Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2009-10-20. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-e2e-rsvp-te-reqts-0 4.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag= 17192rfc_flag=0 ___ IETF-Announce mailing list ietf-annou...@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce ___ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
Last Call: draft-ietf-hokey-preauth-ps (Extensible Authentication Protocol (EAP) Early Authentication Problem Statement) to Informational RFC
The IESG has received a request from the Handover Keying WG (hokey) to consider the following document: - 'Extensible Authentication Protocol (EAP) Early Authentication Problem Statement ' draft-ietf-hokey-preauth-ps-09.txt as an Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the i...@ietf.org mailing lists by 2009-10-21. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-hokey-preauth-ps-09.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=16428rfc_flag=0 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
BEHAVE interim teleconference call
As announced at the Stockholm IETF's BEHAVE meeting, BEHAVE will be using WebEx and PSTN conferencing for the following interim meeting to discuss 6/4 translation and advance those documents: Wednesday, October 21, 7am-9am Pacific Time Per http://www.ietf.org/meeting/cutoff-dates.html#76, the cut-off for revised I-Ds is October 26. Agendas WebEx URL and PSTN dial-in information will be published on BEHAVE's wiki at http://trac.tools.ietf.org/wg/behave/trac/wiki ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
76th IETF - DRAFT Agenda
76th IETF Meeting Hiroshima, Japan November 8-13, 2009 Host: WIDE Only 31 days until the Hiroshima IETF! The DRAFT Agenda is now available at: https://datatracker.ietf.org/meeting/76/agenda.html A more final agenda will be available Friday, 16 October. The IETF agenda is subject to change, up to and during the meeting. Early Bird registration and payment cut-off is Friday, 30 October at 17:00 PDT (24:00 UTC/GMT). Online registration for the IETF meeting is at: http://www.ietf.org/meetings/76/ ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 5522 on Network Mobility Route Optimization Requirements for Operational Use in Aeronautics and Space Exploration Mobile Networks
A new Request for Comments is now available in online RFC libraries. RFC 5522 Title: Network Mobility Route Optimization Requirements for Operational Use in Aeronautics and Space Exploration Mobile Networks Author: W. Eddy, W. Ivancic, T. Davis Status: Informational Date: October 2009 Mailbox:we...@grc.nasa.gov, william.d.ivan...@grc.nasa.gov, terry.l.da...@boeing.com Pages: 31 Characters: 79570 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-mext-aero-reqs-04.txt URL:http://www.rfc-editor.org/rfc/rfc5522.txt This document describes the requirements and desired properties of Network Mobility (NEMO) Route Optimization techniques for use in global-networked communications systems for aeronautics and space exploration. Substantial input to these requirements was given by aeronautical communications experts outside the IETF, including members of the International Civil Aviation Organization (ICAO) and other aeronautical communications standards bodies. This memo provides information for the Internet community. This document is a product of the Mobility EXTensions for IPv6 Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team USC/Information Sciences Institute ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
