From rtg-dir-bounces@ietf.org Mon Apr 02 07:06:10 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYKMQ-0007tL-Mm; Mon, 02 Apr 2007 07:06:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYKMP-0007rA-Gs for rtg-dir@ietf.org; Mon, 02 Apr 2007 07:06:05 -0400 Received: from alnrmhc13.comcast.net ([206.18.177.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYKMO-0006eD-2y for rtg-dir@ietf.org; Mon, 02 Apr 2007 07:06:05 -0400 Received: from frogbits.attlabs.att.com (c-67-188-114-134.hsd1.ca.comcast.net[67.188.114.134]) by comcast.net (alnrmhc13) with ESMTP id <20070402110603b1300jl4bje>; Mon, 2 Apr 2007 11:06:03 +0000 Received: from frogbits.attlabs.att.com (localhost [127.0.0.1]) by frogbits.attlabs.att.com (8.13.4/8.13.4) with ESMTP id l32B030w053759 for ; Mon, 2 Apr 2007 04:00:03 -0700 (PDT) (envelope-from fenner@frogbits.attlabs.att.com) Received: (from fenner@localhost) by frogbits.attlabs.att.com (8.13.4/8.13.4/Submit) id l32B014C053758 for rtg-dir@ietf.org; Mon, 2 Apr 2007 04:00:01 -0700 (PDT) (envelope-from fenner) Date: Mon, 2 Apr 2007 04:00:01 -0700 (PDT) Message-Id: <200704021100.l32B014C053758@frogbits.attlabs.att.com> From: fenner@research.att.com (Bill Fenner) To: rtg-dir@ietf.org (Routing Area Directorate) X-Spam-Score: 0.1 (/) X-Scan-Signature: 162d87dc0b780d17da9b1934777fd451 Subject: IESG agenda for 2007-04-05 telechat. X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rtg-dir-bounces@ietf.org IESG Agenda Good approximation of what will be included in the Agenda of next Telechat (2007-04-05). Updated 2:2:26 EDT, April 2, 2007 ----------------------------------------------------------------------- 1. Administrivia 1.1 Roll Call 1.2 Bash the Agenda 1.3 Approval of the Minutes of the past telechat 1.4 List of Remaining Action Items from Last Telechat 1.5 Review of Projects 2. Protocol Actions Reviews should focus on these questions: "Is this document a reasonable basis on which to build the salient part of the Internet infrastructure? If not, what changes would make it so?" 2.1 WG Submissions 2.1.1 New Item Area Date SEC Feb 24 OpenPGP Message Format (Proposed Standard) - 1 of 6 draft-ietf-openpgp-rfc2440bis-19.txt [Open Web Ballot] Token: Sam Hartman RTG Definition of an IS-IS Link Attribute sub-TLV (Proposed Standard) - 2 of 6 draft-ietf-isis-link-attr-03.txt [Open Web Ballot] Token: Ross Callon SEC Server-based Certificate Validation Protocol (SCVP) (Proposed Standard) - 3 of 6 draft-ietf-pkix-scvp-31.txt [Open Web Ballot] Token: Sam Hartman Extensible Authentication Protocol (EAP) Key INT Management Framework (Proposed Standard) - 4 of 6 draft-ietf-eap-keying-18.txt [Open Web Ballot] Token: Jari Arkko APP WITHIN Search extension to the IMAP Protocol (Proposed Standard) - 5 of 6 draft-ietf-lemonade-search-within-04.txt [Open Web Ballot] Token: Chris Newman INT AII Types for Aggregation (Proposed Standard) - 6 of 6 draft-ietf-pwe3-aii-aggregate-02.txt [Open Web Ballot] Token: Mark Townsley 2.1.2 Returning Item NONE 2.2 Individual Submissions 2.2.1 New Item Area Date GEN POP3 SASL Authentication Mechanism (Proposed Standard) - 1 of 3 draft-siemborski-rfc1734bis-11.txt [Open Web Ballot] Token: Lisa Dusseault GEN Common Local Transmit and Receive Ports (Symmetric RTP) (BCP) - 2 of 3 draft-wing-behave-symmetric-rtprtcp-02.txt [Open Web Ballot] Note: Picked up from RFC-editor independent submission to be a AD-sponsored BCP. Was earlier through an RFC 3932 review, so please re-review. Token: Magnus Westerlund Support for Multiple Hash Algorithms in SEC Cryptographically Generated Addresses (CGAs) (Proposed Standard) - 3 of 3 draft-bagnulo-multiple-hash-cga-03.txt [Open Web Ballot] Note: Document shepherd: James Kempf Token: Russ Housley 2.2.2 Returning Item Area Date GEN Feb 14 Handling Normative References to Standards Track Documents (BCP) - 1 of 1 draft-klensin-norm-ref-04.txt [Open Web Ballot] Note: Target and scope changed from process experiment to BCP Token: Russ Housley 3. Document Actions 3.1 WG Submissions Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.1.1 New Item Area Date TSV Defending TCP Against Spoofing Attacks (Informational) - 1 of 3 draft-ietf-tcpm-tcp-antispoof-06.txt [Open Web Ballot] Note: Document Shepherd: Ted Faber (faber@isi.edu) Token: Lars Eggert INT Analysis of IPv6 Link Models for 802.16 based Networks (Informational) - 2 of 3 draft-ietf-16ng-ipv6-link-model-analysis-03.txt [Open Web Ballot] Note: PROTO Shepherd is Soohong Daniel Park Token: Jari Arkko INT TRILL Routing Requirements in Support of RBridges (Informational) - 3 of 3 draft-ietf-trill-routing-reqs-02.txt [Open Web Ballot] Token: Mark Townsley 3.1.2 Returning Item Area Date INT Link-layer Event Notifications for Detecting Network Attachments (Informational) - 1 of 2 draft-ietf-dna-link-information-06.txt [Open Web Ballot] Token: Jari Arkko INT Five-Document ballot: [Open Web Ballot] - 2 of 2 Host Identity Protocol (Experimental) - 2 of 2 draft-ietf-hip-base-07.txt Using ESP transport format with HIP (Experimental) draft-ietf-hip-esp-05.txt Host Identity Protocol (HIP) Registration Extension (Experimental) draft-ietf-hip-registration-02.txt End-Host Mobility and Multihoming with the Host Identity Protocol (Experimental) draft-ietf-hip-mm-05.txt Host Identity Protocol (HIP) Rendezvous Extension (Experimental) draft-ietf-hip-rvs-05.txt Token: Mark Townsley 3.2 Individual Submissions Via AD Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.2.1 New Item Area Date GEN CableLabs - IETF Standardization Collaboration (Informational) - 1 of 1 draft-mule-ietf-cablelabs-collaboration-03.txt [Open Web Ballot] Token: Jari Arkko 3.2.2 Returning Item NONE 3.3 Independent Submissions Via RFC Editor The IESG will use RFC 3932 responses: 1) The IESG has not found any conflict between this document and IETF work; 2) The IESG thinks that this work is related to IETF work done in WG , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for and should therefore not be published without IETF review and IESG approval; 5) The IESG thinks that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval. Other matters may be recorded in comments to be passed on to the RFC Editor as community review of the document. 3.3.1 New Item NONE 3.3.2 Returning Item NONE 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval NONE 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval NONE 5. IAB News We Can Use 6. Management Issues 6.1 IANA registration for RFC 4235 (Cullen Jennings) 6.2 Designated Expert for RFC 4204 registry (lmp-parameters) [IANA # 68382] (Michelle Cotton) 6.3 Designated Expert for RFC 4430 registry (kink-parameters) [IANA # 68378] (Michelle Cotton) 6.4 IANA experts for RFC 3165 (Dan Romascanu) 6.5 Designated Expert for RFC 4807 registry (sdpActions) [IANA #68396] (Michelle Cotton) 6.6 Designated Expert for RFC 4112 (ecmlv2-parameters) [IANA #68372] (Michelle Cotton) 6.7 Approving selection of the IESG Liason to the IAB (Mark Townsley) 6.8 Approval of the AD sponsoring guidelines ION (Jari Arkko) 6.9 EGLOP Discussion [IANA #68011] (Michelle Cotton) 6.10 Designated Expert for RFC 3936 registry (rsvp-parameters) [IANA # 68374] (Michelle Cotton) 6.11 Designated Expert for RFC 4065 (card and cxtp parameters) [IANA # 68373] (Michelle Cotton) 6.12 Question regarding route-distinguisher-types [IANA #62509] (Michelle Cotton) 6.13 Developing metrics in the IETF (Lars Eggert) 6.14 TMC (Tools Management Committee) (Cullen Jennings) 7. Working Group News From rtg-dir-bounces@ietf.org Mon Apr 02 08:04:57 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYLHJ-0007MC-SK; Mon, 02 Apr 2007 08:04:53 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYLHI-0007Lx-LX for rtg-dir@ietf.org; Mon, 02 Apr 2007 08:04:52 -0400 Received: from heisenberg.zen.co.uk ([212.23.3.141]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYLHD-0004RO-BK for rtg-dir@ietf.org; Mon, 02 Apr 2007 08:04:52 -0400 Received: from [88.96.235.142] (helo=cortex.aria-networks.com) by heisenberg.zen.co.uk with esmtp (Exim 4.50) id 1HYLGm-0004M9-Go for rtg-dir@ietf.org; Mon, 02 Apr 2007 12:04:20 +0000 Received: from your029b8cecfe ([217.158.132.84] RDNS failed) by cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 2 Apr 2007 13:04:19 +0100 Message-ID: <02b601c7751f$0952dd50$0a23fea9@your029b8cecfe> From: "Adrian Farrel" To: "Bill Fenner" , "Routing Area Directorate" References: <200704021100.l32B014C053758@frogbits.attlabs.att.com> Date: Mon, 2 Apr 2007 13:04:06 +0100 Organization: Old Dog Consulting MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-OriginalArrivalTime: 02 Apr 2007 12:04:19.0870 (UTC) FILETIME=[0B6123E0:01C7751F] X-Originating-Heisenberg-IP: [88.96.235.142] X-Spam-Score: 0.2 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Cc: Subject: Re: IESG agenda for 2007-04-05 telechat. X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Routing Area Directorate List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rtg-dir-bounces@ietf.org Hi Bill, Still there? ;-) On... > 6.10 Designated Expert for RFC 3936 registry (rsvp-parameters) [IANA # > 68374] (Michelle Cotton) ... you are, of course, aware that MPLS and CCAMP also make allocations from the rsvp-parameters registry. A From rtg-dir-bounces@ietf.org Mon Apr 02 09:59:24 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYN44-0003Jh-Fn; Mon, 02 Apr 2007 09:59:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYN43-0003JP-7D for rtg-dir@ietf.org; Mon, 02 Apr 2007 09:59:19 -0400 Received: from mail-red.research.att.com ([192.20.225.110]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYN42-0002pq-1m for rtg-dir@ietf.org; Mon, 02 Apr 2007 09:59:19 -0400 Received: from bright.research.att.com (bright.research.att.com [135.207.20.189]) by mail-green.research.att.com (Postfix) with ESMTP id 6C71388ED; Mon, 2 Apr 2007 09:59:13 -0400 (EDT) Received: (from fenner@localhost) by bright.research.att.com (8.13.1/8.12.10/Submit) id l32DxDNF030156; Mon, 2 Apr 2007 06:59:13 -0700 From: Bill Fenner Message-Id: <200704021359.l32DxDNF030156@bright.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: Adrian Farrel (IETF PCE WG) References: <200704021100.l32B014C053758@frogbits.attlabs.att.com> <02b601c7751f$0952dd50$0a23fea9@your029b8cecfe> Date: Mon, 2 Apr 2007 06:59:13 -0700 Versions: dmail (linux) 2.7/makemail 2.14 X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: Routing Area Directorate Subject: Re: IESG agenda for 2007-04-05 telechat. X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rtg-dir-bounces@ietf.org >Still there? ;-) My cron jobs are... >On... > >> 6.10 Designated Expert for RFC 3936 registry (rsvp-parameters) [IANA # >> 68374] (Michelle Cotton) > >.... you are, of course, aware that MPLS and CCAMP also make allocations from >the rsvp-parameters registry. Hopefully the people who will be *on* the call know this too ;-) Bill From rtg-dir-bounces@ietf.org Thu Apr 05 09:47:42 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HZSJM-0001Gi-6S; Thu, 05 Apr 2007 09:47:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HZSJK-0001G7-Mi for rtg-dir@ietf.org; Thu, 05 Apr 2007 09:47:34 -0400 Received: from borg.juniper.net ([207.17.137.119]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HZSJH-0001hO-Da for rtg-dir@ietf.org; Thu, 05 Apr 2007 09:47:34 -0400 Received: from unknown (HELO merlot.juniper.net) ([172.17.27.10]) by borg.juniper.net with ESMTP/TLS/DES-CBC3-SHA; 05 Apr 2007 06:47:31 -0700 X-IronPort-AV: i="4.14,378,1170662400"; d="scan'208"; a="702749903:sNHT31829168" Received: from rcallon-lt1.juniper.net ([172.23.1.243]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id l35DlUJ65771; Thu, 5 Apr 2007 06:47:30 -0700 (PDT) (envelope-from rcallon@juniper.net) Message-Id: <5.0.0.25.2.20070405093903.03644550@zircon.juniper.net> X-Sender: rcallon@zircon.juniper.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 05 Apr 2007 09:45:36 -0400 To: Routing Area Directorate From: Ross Callon Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Cc: rcallon@juniper.net, dward@cisco.com Subject: Volunteer Needed to review draft-ietf-16ng-ipv6-link-model-analysis X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rtg-dir-bounces@ietf.org I would like one or two routing-clueful volunteers to review: Analysis of IPv6 Link Models for 802.16 based Networks draft-ietf-16ng-ipv6-link-model-analysis-03.txt particularly from the perspective of implications of this document on routing protocols or methods for routing over the 802.16 network models described. This document was supposed to be on the agenda for today's IESG call, but I have deferred it for two weeks, implying that I would need a review back by two weeks from yesterday. From the introduction: 802.16 [4] [5] is a point-to-multipoint connection oriented access technology for the last mile without bi-directional native multicast support. 802.16 has defined only downlink multicast support. This leads to two methods for running IP protocols that traditionally assume the availability of multicast at the link layer. One method is to use bridging e.g. 802.1D [6] to support bi-directional multicast, another method is to treat the 802.16 MAC transport connections between an MS and BS as point-to-point IP link, so that, the IP protocols (e.g. ARP, IPv6 Neighbor Discovery) can be run without any problems. This is further complicated by the definition of commercial network models like WiMAX, which defines the WiMAX transport connection that extend the 802.16 MAC transport connection all the way to an access router by using a tunnel between the base station and the access router. This leads to multiple ways of deploying IP over 802.16 based networks. In reading this through, it seems pretty clear that there are routing implications of the model chosen, which are not described in the document. Thanks, Ross From rtg-dir-bounces@ietf.org Mon Apr 16 07:06:12 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HdP2A-0004c6-Tf; Mon, 16 Apr 2007 07:06:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HdP29-0004bt-DC for rtg-dir@ietf.org; Mon, 16 Apr 2007 07:06:09 -0400 Received: from alnrmhc13.comcast.net ([206.18.177.53]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HdP27-0003lD-Qd for rtg-dir@ietf.org; Mon, 16 Apr 2007 07:06:09 -0400 Received: from frogbits.attlabs.att.com (c-67-188-114-134.hsd1.ca.comcast.net[67.188.114.134]) by comcast.net (alnrmhc13) with ESMTP id <20070416110607b1300jlsb7e>; Mon, 16 Apr 2007 11:06:07 +0000 Received: from frogbits.attlabs.att.com (localhost [127.0.0.1]) by frogbits.attlabs.att.com (8.13.4/8.13.4) with ESMTP id l3GB05FS012400 for ; Mon, 16 Apr 2007 04:00:05 -0700 (PDT) (envelope-from fenner@frogbits.attlabs.att.com) Received: (from fenner@localhost) by frogbits.attlabs.att.com (8.13.4/8.13.4/Submit) id l3GB051g012399 for rtg-dir@ietf.org; Mon, 16 Apr 2007 04:00:05 -0700 (PDT) (envelope-from fenner) Date: Mon, 16 Apr 2007 04:00:05 -0700 (PDT) Message-Id: <200704161100.l3GB051g012399@frogbits.attlabs.att.com> From: fenner@research.att.com (Bill Fenner) To: rtg-dir@ietf.org (Routing Area Directorate) X-Spam-Score: 0.1 (/) X-Scan-Signature: fe105289edd72640d9f392da880eefa2 Subject: IESG agenda for 2007-04-19 telechat. X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rtg-dir-bounces@ietf.org IESG Agenda Good approximation of what will be included in the Agenda of next Telechat (2007-04-19). Updated 2:2:26 EDT, April 16, 2007 ----------------------------------------------------------------------- 1. Administrivia 1.1 Roll Call 1.2 Bash the Agenda 1.3 Approval of the Minutes of the past telechat 1.4 List of Remaining Action Items from Last Telechat 1.5 Review of Projects 2. Protocol Actions Reviews should focus on these questions: "Is this document a reasonable basis on which to build the salient part of the Internet infrastructure? If not, what changes would make it so?" 2.1 WG Submissions 2.1.1 New Item Area Date RAI Presence Authorization Rules (Proposed Standard) - 1 of 5 draft-ietf-simple-presence-rules-09.txt [Open Web Ballot] Token: Jon Peterson Definitions of Managed Objects for iSNS TSV (Internet Storage Name Service) (Proposed Standard) - 2 of 5 draft-ietf-ips-isns-mib-11.txt [Open Web Ballot] Note: PROTO Shepherd: David Black (Black_David@emc.com) MIB Doctor: Bert Wijnen (bwijnen@lucent.com) Initial expert review: Keith McCloghrie (kzm@cisco.com) Token: Lars Eggert TSV Forward Error Correction (FEC) Building Block (Proposed Standard) - 3 of 5 draft-ietf-rmt-fec-bb-revised-06.txt [Open Web Ballot] Token: Magnus Westerlund IPv6 Over the IP Specific part of the Packet INT Convergence sublayer in 802.16 Networks (Proposed Standard) - 4 of 5 draft-ietf-16ng-ipv6-over-ipv6cs-09.txt Note: NOTE: There are some LC and IEEE-review comments pending Token: Jari Arkko TSV NAT Behavioral Requirements for TCP (BCP) - 5 of 5 draft-ietf-behave-tcp-06.txt [Open Web Ballot] Token: Magnus Westerlund 2.1.2 Returning Item Area Date SEC Lightweight OCSP Profile for High Volume Environments (Proposed Standard) - 1 of 1 draft-ietf-pkix-lightweight-ocsp-profile-08.txt [Open Web Ballot] Token: Russ Housley 2.2 Individual Submissions 2.2.1 New Item Area Date APP IMAP Extension for SASL Initial Client Response (Proposed Standard) - 1 of 1 draft-siemborski-imap-sasl-initial-response-06.txt [Open Web Ballot] Token: Chris Newman 2.2.2 Returning Item NONE 3. Document Actions 3.1 WG Submissions Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.1.1 New Item Area Date INT Analysis of IPv6 Link Models for 802.16 based Networks (Informational) - 1 of 2 draft-ietf-16ng-ipv6-link-model-analysis-03.txt [Open Web Ballot] Note: PROTO Shepherd is Soohong Daniel Park Token: Jari Arkko INT TRILL Routing Requirements in Support of RBridges (Informational) - 2 of 2 draft-ietf-trill-routing-reqs-02.txt [Open Web Ballot] Token: Mark Townsley 3.1.2 Returning Item Area Date INT Five-Document ballot: [Open Web Ballot] - 1 of 1 Host Identity Protocol (Experimental) - 1 of 1 draft-ietf-hip-base-07.txt Using ESP transport format with HIP (Experimental) draft-ietf-hip-esp-05.txt Host Identity Protocol (HIP) Registration Extension (Experimental) draft-ietf-hip-registration-02.txt End-Host Mobility and Multihoming with the Host Identity Protocol (Experimental) draft-ietf-hip-mm-05.txt Host Identity Protocol (HIP) Rendezvous Extension (Experimental) draft-ietf-hip-rvs-05.txt Token: Mark Townsley 3.2 Individual Submissions Via AD Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.2.1 New Item Area Date The P-Answer-State Header Extension to the Session RAI Initiation Protocol for the Open Mobile Alliance Push-to-talk over Cellular (Informational) - 1 of 1 draft-allen-sipping-poc-p-answer-state-header-05.txt [Open Web Ballot] Note: SIPPING RFC 3427 Expert Reviewer is Gonzalo Camarillo; dependency of OMA Token: Jon Peterson 3.2.2 Returning Item NONE 3.3 Independent Submissions Via RFC Editor The IESG will use RFC 3932 responses: 1) The IESG has not found any conflict between this document and IETF work; 2) The IESG thinks that this work is related to IETF work done in WG , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for and should therefore not be published without IETF review and IESG approval; 5) The IESG thinks that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval. Other matters may be recorded in comments to be passed on to the RFC Editor as community review of the document. 3.3.1 New Item Area Date OPS Wireless LAN Control Protocol (WiCoP) (Informational) - 1 of 2 draft-iino-capwap-wicop-02.txt [Open Web Ballot] Note: This document is an independent submission via the RFC Editor. In conformace with RFC 3932, Section 4, the IESG requests the publication of the following note: "This RFC documents the WiCoP protocol as it was when submitted to the IETF as a basis for further work in the CAPWAP WG, and therefore it may resemble a current IETF work in progress or a published IETF work. This RFC itself is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this RFC for any purpose, and in particular notes that it has not had complete IETF review for such things as security, congestion control, or inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its discretion." Token: Dan Romascanu OPS Light Weight Access Point Protocol (Informational) - 2 of 2 draft-ohara-capwap-lwapp-04.txt [Open Web Ballot] Note: This document is an independent submission via the RFC Editor. In conformace with RFC 3932, Section 4, the IESG requests the publication of the following note: "This RFC documents the LWAPP protocol as it was when submitted to the IETF as a basis for further work in the CAPWAP WG, and therefore it may resemble a current IETF work in progress or a published IETF work. This RFC itself is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this RFC for any purpose, and in particular notes that it has not had complete IETF review for such things as security, congestion control, or inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its discretion." Token: Dan Romascanu 3.3.2 Returning Item Area Date OPS SLAPP : Secure Light Access Point Protocol (Informational) - 1 of 1 draft-narasimhan-ietf-slapp-01.txt [Open Web Ballot] Note: This document is an independent submission via the RFC Editor. In conformace with RFC 3932, Section 4, the IESG requests the publication of the following note: "This RFC documents the SLAPP protocol as it was when submitted to the IETF as a basis for further work in the CAPWAP WG, and therefore it may resemble a current IETF work in progress or a published IETF work. This RFC itself is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this RFC for any purpose, and in particular notes that it has not had complete IETF review for such things as security, congestion control, or inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its discretion." Token: Dan Romascanu 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval NONE 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval NONE 5. IAB News We Can Use 6. Management Issues 6.1 EXECUTIVE SESSION: Confirmation of ISOC BoT Appointment (Russ Housley) 6.2 IANA designated expert for RFC4728 6.3 IANA designated expert for RFC3936 6.4 IANA designated expert for RFC4204 7. Working Group News