From michelle.cotton@icann.org Thu Apr 2 14:43:16 2009 Return-Path: X-Original-To: mboned@core3.amsl.com Delivered-To: mboned@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D061A3A6CBB for ; Thu, 2 Apr 2009 14:43:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.332 X-Spam-Level: X-Spam-Status: No, score=-6.332 tagged_above=-999 required=5 tests=[AWL=0.266, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XjBGYEmH1nbj for ; Thu, 2 Apr 2009 14:43:15 -0700 (PDT) Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id BE1C83A6A71 for ; Thu, 2 Apr 2009 14:43:15 -0700 (PDT) Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.233]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Thu, 2 Apr 2009 14:44:17 -0700 From: Michelle Cotton To: "mboned@ietf.org" Date: Thu, 2 Apr 2009 14:44:43 -0700 Thread-Topic: Suggested format changes for address prefixes in ipv6-multicast-addresses registry Thread-Index: Acmy46faLWyGZROMTvO0A2HTlD+uBQA4chk+AAWy07Y= Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_C5FA7FDB15B36michellecottonicannorg_" MIME-Version: 1.0 Subject: [MBONED] Suggested format changes for address prefixes in ipv6-multicast-addresses registry X-BeenThere: mboned@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mail List for the Mboned Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2009 21:43:16 -0000 --_000_C5FA7FDB15B36michellecottonicannorg_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MBONED WG: It was recently suggested that we update the format of the representation o= f some of the IPv6 multicast registrations in the following registry: http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-add= resses.xhtml Here are the suggested changes for the IPv6 multicast address registry. - Solicited Node Multicast addresses: FF02::1:FFXX:XXXX can be changed to FF02:0:0:0:0:1:FF00::/104 - Service Location, Version 2 Multicast addresses: FF0X:0:0:0:0:0:1:1000-FF0X:0:0:0:0:0:13FF can be changed to FF0X::1:1000/118. It also needs to be moved from the Site-local table to the Variable scope table - SAP Dynamic multicast addresses: FF0X:0:0:0:0:0:2:8000-FF0X:0:0:0:0:0:FFFF can be changed to FF0X::8000/113 - SSM Addresses: FF3X:0::0-FF3X:0::FFFF:FFFF can be changed to FF3X:0::/32 - SSM IANA allocation range can be noted as: FF3X::4000:0 Reserved FF3X::4000:0/98 IANA Allocation FF3X::8000:0/97 Local Allocation Thank you to Brian Haberman for theses suggestions. Please let us know if = there are any strong objections to making these changes in the registry. W= e would like to make the changes soon, so please respond if there are any i= ssues by April 16th. Thank you, Michelle Cotton IANA --_000_C5FA7FDB15B36michellecottonicannorg_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Suggested format changes for address prefixes in ipv6-multicast-addr= esses registry MBONED WG:

It was recently suggested that we update the format of the representation o= f some of the IPv6 multicast registrations in the following registry:

http://www.iana.org/assignments/ipv6-multicast-add= resses/ipv6-multicast-addresses.xhtml

Here are the suggested changes for the IPv6 multicast address registry. &nb= sp;

- Solicited Node Multicast addresses: FF02::1:FFXX:XXXX can be changed
to FF02:0:0:0:0:1:FF00::/104

- Service Location, Version 2 Multicast addresses:
FF0X:0:0:0:0:0:1:1000-FF0X:0:0:0:0:0:13FF can be changed to
FF0X::1:1000/118.  It also needs to be moved from the Site-local table=
to the Variable scope table

- SAP Dynamic multicast addresses:
FF0X:0:0:0:0:0:2:8000-FF0X:0:0:0:0:0:FFFF can be changed to FF0X::8000/113<= BR>
- SSM Addresses: FF3X:0::0-FF3X:0::FFFF:FFFF can be changed to FF3X:0::/32<= BR>
- SSM IANA allocation range can be noted as:
FF3X::4000:0 Reserved
FF3X::4000:0/98 IANA Allocation
FF3X::8000:0/97 Local Allocation

Thank you to Brian Haberman for theses suggestions.  Please let us kno= w if there are any strong objections to making these changes in the registr= y.  We would like to make the changes soon, so please respond if there= are any issues by April 16th.

Thank you,

Michelle Cotton
IANA
 --_000_C5FA7FDB15B36michellecottonicannorg_-- From A.Hoenes@tr-sys.de Fri Apr 3 01:08:16 2009 Return-Path: X-Original-To: mboned@core3.amsl.com Delivered-To: mboned@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C31753A68C7 for ; Fri, 3 Apr 2009 01:08:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.849 X-Spam-Level: * X-Spam-Status: No, score=1.849 tagged_above=-999 required=5 tests=[AWL=0.598, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zmuPPgvgTJL7 for ; Fri, 3 Apr 2009 01:08:16 -0700 (PDT) Received: from WOTAN.TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by core3.amsl.com (Postfix) with ESMTP id 2FAAF3A691B for ; Fri, 3 Apr 2009 01:08:14 -0700 (PDT) Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3) id AA116756034; Fri, 3 Apr 2009 10:07:14 +0200 Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id KAA25394; Fri, 3 Apr 2009 10:07:13 +0200 (MESZ) From: Alfred =?hp-roman8?B?SM5uZXM=?= Message-Id: <200904030807.KAA25394@TR-Sys.de> To: michell.cotton@icann.org, mboned@ietf.org Date: Fri, 3 Apr 2009 10:07:12 +0200 (MESZ) X-Mailer: ELM [$Revision: 1.17.214.3 $] Mime-Version: 1.0 Content-Type: text/plain; charset=hp-roman8 Content-Transfer-Encoding: 8bit Subject: Re: [MBONED] Suggested format changes for address prefixes in ipv6-multicast-addresses registry X-BeenThere: mboned@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mail List for the Mboned Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2009 08:08:16 -0000 Michelle, generally, I agree with the proposed changes in the ipv6-multicast-addresses registry, ... > - Solicited Node Multicast addresses: > FF02::1:FFXX:XXXX can be changed to FF02:0:0:0:0:1:FF00::/104 > > - Service Location, Version 2 Multicast addresses: > FF0X:0:0:0:0:0:1:1000-FF0X:0:0:0:0:0:13FF can be changed to > FF0X::1:1000/118. > It also needs to be moved from the Site-local table > to the Variable scope table > > ... ... but for consistency in style and improved readability, I suggest to modify the first item in the proposal to also use an *internal* "::", and specify the trailing part of the prefix explicitely, as in the second instance (and others). So I suggest using instead of your first item: - Solicited Node Multicast addresses: FF02::1:FFXX:XXXX can be changed to FF02::1:FF00:0000/104 ^^ ^^^^^ This way all prefixes with long runs of zero bits after the leading 16-bit group would be uniformly written as FFxx::___ , with the "::" after the first 16-bit group. Kind regards, Alfred HÎnes. -- +------------------------+--------------------------------------------+ | TR-Sys Alfred Hoenes | Alfred Hoenes Dipl.-Math., Dipl.-Phys. | | Gerlinger Strasse 12 | Phone: (+49)7156/9635-0, Fax: -18 | | D-71254 Ditzingen | E-Mail: ah@TR-Sys.de | +------------------------+--------------------------------------------+ From tme@multicasttech.com Mon Apr 13 16:12:45 2009 Return-Path: X-Original-To: mboned@core3.amsl.com Delivered-To: mboned@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BCD533A6963 for ; Mon, 13 Apr 2009 16:12:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.49 X-Spam-Level: X-Spam-Status: No, score=-101.49 tagged_above=-999 required=5 tests=[AWL=-1.931, BAYES_05=-1.11, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EvwL9rScNQUf for ; Mon, 13 Apr 2009 16:12:45 -0700 (PDT) Received: from mail.americafree.tv (unknown [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id 276C83A67B1 for ; Mon, 13 Apr 2009 16:12:45 -0700 (PDT) Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 044D03945351 for ; Mon, 13 Apr 2009 18:55:33 -0400 (EDT) Message-Id: <22CEF9FB-70BB-4085-8459-2BDD6CAFFD5C@multicasttech.com> From: Marshall Eubanks To: mboned@ietf.org Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 13 Apr 2009 18:55:33 -0400 X-Mailer: Apple Mail (2.930.3) Subject: [MBONED] test X-BeenThere: mboned@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mail List for the Mboned Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2009 23:12:45 -0000 Please ignore, this is a test of the mail system. From michelle.cotton@icann.org Tue Apr 14 09:49:08 2009 Return-Path: X-Original-To: mboned@core3.amsl.com Delivered-To: mboned@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB15A3A6847 for ; Tue, 14 Apr 2009 09:49:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.326 X-Spam-Level: X-Spam-Status: No, score=-6.326 tagged_above=-999 required=5 tests=[AWL=0.272, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cSJjT5lyjDnh for ; Tue, 14 Apr 2009 09:49:07 -0700 (PDT) Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by core3.amsl.com (Postfix) with ESMTP id D01463A67D4 for ; Tue, 14 Apr 2009 09:49:07 -0700 (PDT) Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.233]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Tue, 14 Apr 2009 09:50:19 -0700 From: Michelle Cotton To: "mboned@ietf.org" Date: Tue, 14 Apr 2009 09:50:48 -0700 Thread-Topic: Suggested format changes for address prefixes in ipv6-multicast-addresses registry Thread-Index: Acmy46faLWyGZROMTvO0A2HTlD+uBQA4chk+AAWy07YCUTtrdA== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_C60A0CF81611Bmichellecottonicannorg_" MIME-Version: 1.0 Subject: [MBONED] FW: Suggested format changes for address prefixes in ipv6-multicast-addresses registry X-BeenThere: mboned@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mail List for the Mboned Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2009 16:49:08 -0000 --_000_C60A0CF81611Bmichellecottonicannorg_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Just a friendly reminder, if anyone has comments regarding this we were hop= ing to get responses by the 16th. (Thank you Alfred for your comments) Best regards, Michelle IANA ------ Forwarded Message From: Michelle Cotton Date: Thu, 02 Apr 2009 14:44:43 -0700 To: Conversation: Suggested format changes for address prefixes in ipv6-multica= st-addresses registry Subject: Suggested format changes for address prefixes in ipv6-multicast-ad= dresses registry MBONED WG: It was recently suggested that we update the format of the representation o= f some of the IPv6 multicast registrations in the following registry: http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-add= resses.xhtml Here are the suggested changes for the IPv6 multicast address registry. - Solicited Node Multicast addresses: FF02::1:FFXX:XXXX can be changed to FF02:0:0:0:0:1:FF00::/104 - Service Location, Version 2 Multicast addresses: FF0X:0:0:0:0:0:1:1000-FF0X:0:0:0:0:0:13FF can be changed to FF0X::1:1000/118. It also needs to be moved from the Site-local table to the Variable scope table - SAP Dynamic multicast addresses: FF0X:0:0:0:0:0:2:8000-FF0X:0:0:0:0:0:FFFF can be changed to FF0X::8000/113 - SSM Addresses: FF3X:0::0-FF3X:0::FFFF:FFFF can be changed to FF3X:0::/32 - SSM IANA allocation range can be noted as: FF3X::4000:0 Reserved FF3X::4000:0/98 IANA Allocation FF3X::8000:0/97 Local Allocation Thank you to Brian Haberman for theses suggestions. Please let us know if = there are any strong objections to making these changes in the registry. W= e would like to make the changes soon, so please respond if there are any i= ssues by April 16th. Thank you, Michelle Cotton IANA ------ End of Forwarded Message --_000_C60A0CF81611Bmichellecottonicannorg_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable FW: Suggested format changes for address prefixes in ipv6-multicast-= addresses registry Just a friendly reminder, if anyone has comments regarding this we we= re hoping to get responses by the 16th.
(Thank you Alfred for your comments)

Best regards,

Michelle
IANA

------ Forwarded Message
From: Michelle Cotton <mich= elle.cotton@icann.org>
Date: Thu, 02 Apr 2009 14:44:43 -0700
To: <mboned@ietf.org>
Conversation: Suggested format changes for address prefixes in ipv6-= multicast-addresses registry
Subject: Suggested format changes for address prefixes in ipv6-multi= cast-addresses registry

MBONED WG:

It was recently suggested that we update the format of the representation o= f some of the IPv6 multicast registrations in the following registry:

http://www.iana.org/assignments/ipv6-multicast-add= resses/ipv6-multicast-addresses.xhtml

Here are the suggested changes for the IPv6 multicast address registry. &nb= sp;

- Solicited Node Multicast addresses: FF02::1:FFXX:XXXX can be changed
to FF02:0:0:0:0:1:FF00::/104

- Service Location, Version 2 Multicast addresses:
FF0X:0:0:0:0:0:1:1000-FF0X:0:0:0:0:0:13FF can be changed to
FF0X::1:1000/118.  It also needs to be moved from the Site-local table=
to the Variable scope table

- SAP Dynamic multicast addresses:
FF0X:0:0:0:0:0:2:8000-FF0X:0:0:0:0:0:FFFF can be changed to FF0X::8000/113<= BR>
- SSM Addresses: FF3X:0::0-FF3X:0::FFFF:FFFF can be changed to FF3X:0::/32<= BR>
- SSM IANA allocation range can be noted as:
FF3X::4000:0 Reserved
FF3X::4000:0/98 IANA Allocation
FF3X::8000:0/97 Local Allocation

Thank you to Brian Haberman for theses suggestions.  Please let us kno= w if there are any strong objections to making these changes in the registr= y.  We would like to make the changes soon, so please respond if there= are any issues by April 16th.

Thank you,

Michelle Cotton
IANA

------ End of Forwarded Message
 --_000_C60A0CF81611Bmichellecottonicannorg_-- From root@core3.amsl.com Wed Apr 15 11:15:02 2009 Return-Path: X-Original-To: mboned@ietf.org Delivered-To: mboned@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 0999C3A6B07; Wed, 15 Apr 2009 11:15:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090415181502.0999C3A6B07@core3.amsl.com> Date: Wed, 15 Apr 2009 11:15:02 -0700 (PDT) Cc: mboned@ietf.org Subject: [MBONED] I-D Action:draft-ietf-mboned-rfc3171bis-07.txt X-BeenThere: mboned@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mail List for the Mboned Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2009 18:15:02 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the MBONE Deployment Working Group of the IETF. Title : IANA Guidelines for IPv4 Multicast Address Assignments Author(s) : M. Cotton, et al. Filename : draft-ietf-mboned-rfc3171bis-07.txt Pages : 11 Date : 2009-04-15 This document provides guidance for the Internet Assigned Numbers Authority (IANA) in assigning IPv4 multicast addresses. It obsoletes RFC 3171 and RFC 3138. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mboned-rfc3171bis-07.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-mboned-rfc3171bis-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-04-15110825.I-D@ietf.org> --NextPart-- From michelle.cotton@icann.org Wed Apr 15 11:23:41 2009 Return-Path: X-Original-To: mboned@core3.amsl.com Delivered-To: mboned@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 377B928C121 for ; Wed, 15 Apr 2009 11:23:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.333 X-Spam-Level: X-Spam-Status: No, score=-6.333 tagged_above=-999 required=5 tests=[AWL=0.265, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VY5Ax1Q86zBx for ; Wed, 15 Apr 2009 11:23:40 -0700 (PDT) Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id 5AD7828C180 for ; Wed, 15 Apr 2009 11:23:40 -0700 (PDT) Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.233]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Wed, 15 Apr 2009 11:24:52 -0700 From: Michelle Cotton To: "mboned@ietf.org" Date: Wed, 15 Apr 2009 11:25:21 -0700 Thread-Topic: [MBONED] I-D Action:draft-ietf-mboned-rfc3171bis-07.txt Thread-Index: Acm99lGhgRVWvXLIRj6IO7CIxPz1/AAATdg1 Message-ID: In-Reply-To: <20090415181502.0999C3A6B07@core3.amsl.com> Accept-Language: en-US Content-Language: en X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/mixed; boundary="_004_C60B74A2161E3michellecottonicannorg_" MIME-Version: 1.0 Subject: [MBONED] FW: I-D Action:draft-ietf-mboned-rfc3171bis-07.txt X-BeenThere: mboned@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mail List for the Mboned Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Apr 2009 18:23:41 -0000 --_004_C60B74A2161E3michellecottonicannorg_ Content-Type: multipart/alternative; boundary="_000_C60B74A2161E3michellecottonicannorg_" --_000_C60B74A2161E3michellecottonicannorg_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MBONED WG: A new version of 3171bis has been posted. The only issue not covered in th= is document is regarding the expert review policy. It was agreed early on = in the process of writing 3171bis that we would address that in a separate = document. Minor format/style issues will also be addressed by the RFC-Edit= or. Are there any more comments for this document? If there are no additional comments, Marshall what are our next steps here? Michelle Cotton IANA ------ Forwarded Message From: Date: Wed, 15 Apr 2009 11:15:02 -0700 To: Cc: Subject: [MBONED] I-D Action:draft-ietf-mboned-rfc3171bis-07.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the MBONE Deployment Working Group of the IETF= . Title : IANA Guidelines for IPv4 Multicast Address Assign= ments Author(s) : M. Cotton, et al. Filename : draft-ietf-mboned-rfc3171bis-07.txt Pages : 11 Date : 2009-04-15 This document provides guidance for the Internet Assigned Numbers Authority (IANA) in assigning IPv4 multicast addresses. It obsoletes RFC 3171 and RFC 3138. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mboned-rfc3171bis-07.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------ End of Forwarded Message --_000_C60B74A2161E3michellecottonicannorg_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable FW: [MBONED] I-D Action:draft-ietf-mboned-rfc3171bis-07.txt MBONED WG:

A new version of 3171bis has been posted.  The only issue not covered = in this document is regarding the expert review policy.  It was agreed= early on in the process of writing 3171bis that we would address that in a= separate document.  Minor format/style issues will also be addressed = by the RFC-Editor.

Are there any more comments for this document?
If there are no additional comments, Marshall what are our next steps here?=

Michelle Cotton
IANA


------ Forwarded Message
From: <Internet-Drafts@ietf.= org>
Date: Wed, 15 Apr 2009 11:15:02 -0700
To: <i-d-announce@ietf.org&= gt;
Cc: <mboned@ietf.org>
Subject: [MBONED] I-D Action:draft-ietf-mboned-rfc3171bis-07.txt

A New Internet-Draft is available from the on-line Internet-Drafts director= ies.
This draft is a work item of the MBONE Deployment Working Group of the IETF= .


        Title    &nb= sp;      : IANA Guidelines for IPv4 Multicast= Address Assignments
        Author(s)    = ;   : M. Cotton, et al.
        Filename    =     : draft-ietf-mboned-rfc3171bis-07.txt
        Pages    &nb= sp;      : 11
        Date    &nbs= p;       : 2009-04-15

This document provides guidance for the Internet Assigned Numbers
Authority (IANA) in assigning IPv4 multicast addresses.  It obsoletes<= BR> RFC 3171 and RFC 3138.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mboned-rfc3171bis-0= 7.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet= -drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


------ End of Forwarded Message
 --_000_C60B74A2161E3michellecottonicannorg_-- --_004_C60B74A2161E3michellecottonicannorg_ Content-Type: application/octet-stream; name="ATT00001.txt" Content-Description: ATT00001.txt Content-Disposition: attachment; filename="ATT00001.txt"; size=133; creation-date="Wed, 15 Apr 2009 11:24:53 GMT"; modification-date="Wed, 15 Apr 2009 11:24:53 GMT" Content-Transfer-Encoding: base64 X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCk1CT05FRCBt YWlsaW5nIGxpc3QNCk1CT05FREBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h bi9saXN0aW5mby9tYm9uZWQNCg== --_004_C60B74A2161E3michellecottonicannorg_-- From lenny@juniper.net Mon Apr 27 13:53:15 2009 Return-Path: X-Original-To: mboned@core3.amsl.com Delivered-To: mboned@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 401D53A6933 for ; Mon, 27 Apr 2009 13:53:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.556 X-Spam-Level: X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SIQtlNip9m7Y for ; Mon, 27 Apr 2009 13:53:14 -0700 (PDT) Received: from chip3og58.obsmtp.com (chip3og58.obsmtp.com [64.18.14.181]) by core3.amsl.com (Postfix) with ESMTP id 5077A3A6863 for ; Mon, 27 Apr 2009 13:53:14 -0700 (PDT) Received: from source ([66.129.224.36]) (using TLSv1) by chip3ob58.postini.com ([64.18.6.12]) with SMTP ID DSNKSfYbihU+NH2cwthqWIG/V0EtTK8Jnj/m@postini.com; Mon, 27 Apr 2009 13:54:35 PDT Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.340.0; Mon, 27 Apr 2009 13:42:47 -0700 Received: from p-emlb02-sac.jnpr.net ([66.129.254.47]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 27 Apr 2009 13:42:47 -0700 Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb02-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 27 Apr 2009 13:42:47 -0700 Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 27 Apr 2009 13:42:46 -0700 Received: from zircon.juniper.net (zircon.juniper.net [172.17.28.113]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id n3RKgkM92799 for ; Mon, 27 Apr 2009 13:42:46 -0700 (PDT) (envelope-from lenny@juniper.net) Received: from zircon.juniper.net (localhost [127.0.0.1]) by zircon.juniper.net (8.12.11/8.12.3) with ESMTP id n3RKgkma080330 for ; Mon, 27 Apr 2009 13:42:46 -0700 (PDT) (envelope-from lenny@juniper.net) Received: from localhost (lenny@localhost) by zircon.juniper.net (8.12.11/8.12.3/Submit) with ESMTP id n3RKgkfu080327 for ; Mon, 27 Apr 2009 13:42:46 -0700 (PDT) X-Authentication-Warning: zircon.juniper.net: lenny owned process doing -bs Date: Mon, 27 Apr 2009 13:42:46 -0700 From: Leonard Giuliano To: mboned@ietf.org Message-ID: <20090427133256.L77049@zircon.juniper.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII"; format=flowed X-OriginalArrivalTime: 27 Apr 2009 20:42:46.0767 (UTC) FILETIME=[B8D3EFF0:01C9C778] Subject: [MBONED] IETF 74 draft meeting minutes X-BeenThere: mboned@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mail List for the Mboned Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Apr 2009 20:53:15 -0000 Draft meeting minutes from IETF 74 are now available. http://www.ietf.org/proceedings/09mar/agenda/mboned.txt Special thanks to Marco for taking notes. If you have any corrections, please let us know. Thanks, Marshall, Greg and Lenny From lenny@juniper.net Mon Apr 27 13:54:39 2009 Return-Path: X-Original-To: mboned@core3.amsl.com Delivered-To: mboned@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8081128C1B8 for ; Mon, 27 Apr 2009 13:54:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.562 X-Spam-Level: X-Spam-Status: No, score=-6.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HYyiwIZA1MKc for ; Mon, 27 Apr 2009 13:54:38 -0700 (PDT) Received: from chip3og58.obsmtp.com (chip3og58.obsmtp.com [64.18.14.181]) by core3.amsl.com (Postfix) with ESMTP id 4C9343A6AC0 for ; Mon, 27 Apr 2009 13:54:38 -0700 (PDT) Received: from source ([66.129.224.36]) (using TLSv1) by chip3ob58.postini.com ([64.18.6.12]) with SMTP ID DSNKSfYb34ebAPo3C0+xcx5uMPdWyvP5Ja26@postini.com; Mon, 27 Apr 2009 13:55:59 PDT Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.340.0; Mon, 27 Apr 2009 13:44:12 -0700 Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 27 Apr 2009 13:44:12 -0700 Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 27 Apr 2009 13:44:12 -0700 Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 27 Apr 2009 13:44:12 -0700 Received: from zircon.juniper.net (zircon.juniper.net [172.17.28.113]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id n3RKiBM93820 for ; Mon, 27 Apr 2009 13:44:11 -0700 (PDT) (envelope-from lenny@juniper.net) Received: from zircon.juniper.net (localhost [127.0.0.1]) by zircon.juniper.net (8.12.11/8.12.3) with ESMTP id n3RKiBdg080379 for ; Mon, 27 Apr 2009 13:44:11 -0700 (PDT) (envelope-from lenny@juniper.net) Received: from localhost (lenny@localhost) by zircon.juniper.net (8.12.11/8.12.3/Submit) with ESMTP id n3RKiB8B080376 for ; Mon, 27 Apr 2009 13:44:11 -0700 (PDT) X-Authentication-Warning: zircon.juniper.net: lenny owned process doing -bs Date: Mon, 27 Apr 2009 13:44:11 -0700 From: Leonard Giuliano To: mboned@ietf.org In-Reply-To: <20090427133256.L77049@zircon.juniper.net> Message-ID: <20090427134336.Y80028@zircon.juniper.net> References: <20090427133256.L77049@zircon.juniper.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-OriginalArrivalTime: 27 Apr 2009 20:44:12.0015 (UTC) FILETIME=[EBA3BFF0:01C9C778] Subject: Re: [MBONED] IETF 74 draft meeting minutes X-BeenThere: mboned@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mail List for the Mboned Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Apr 2009 20:54:39 -0000 Sorry, wrong link. Correct link is: http://www.ietf.org/proceedings/09mar/minutes/mboned.txt On Mon, 27 Apr 2009, Leonard Giuliano wrote: -) -) Draft meeting minutes from IETF 74 are now available. -) -) http://www.ietf.org/proceedings/09mar/agenda/mboned.txt -) -) Special thanks to Marco for taking notes. If you have any corrections, -) please let us know. -) -) -) Thanks, -) Marshall, Greg and Lenny -) From tme@multicasttech.com Mon Apr 27 14:29:09 2009 Return-Path: X-Original-To: mboned@core3.amsl.com Delivered-To: mboned@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 609743A680D for ; Mon, 27 Apr 2009 14:29:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.648 X-Spam-Level: X-Spam-Status: No, score=-102.648 tagged_above=-999 required=5 tests=[AWL=-0.649, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6OLEIgkuCyKC for ; Mon, 27 Apr 2009 14:29:08 -0700 (PDT) Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id A87423A6C46 for ; Mon, 27 Apr 2009 14:29:07 -0700 (PDT) Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 759873AEA9F0 for ; Mon, 27 Apr 2009 17:30:27 -0400 (EDT) Message-Id: From: Marshall Eubanks To: mboned@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 27 Apr 2009 17:30:25 -0400 References: <20090427145627.971283A6CBC@core3.amsl.com> X-Mailer: Apple Mail (2.930.3) Subject: [MBONED] Fwd: 75th IETF - Working Group/BOF Scheduling X-BeenThere: mboned@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mail List for the Mboned Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Apr 2009 21:29:09 -0000 Begin forwarded message: > From: IETF Agenda > Date: April 27, 2009 10:56:27 AM EDT > To: Working Group Chairs > Cc: irsg@isi.edu, bofchairs@ietf.org > Subject: 75th IETF - Working Group/BOF Scheduling > > ----------------------------------------------------------------- > 75th IETF =96 Stockholm, Sweden > Meeting Dates: July 26-31, 2009 > Host: .SE > ----------------------------------------------------------------- > IETF meetings start Monday morning and run through Friday mid-=20 > afternoon > (15:15). > > We are accepting scheduling requests for all Working Groups and BOFs > starting. The milestones and deadlines for scheduling-related =20 > activities > are as follows: > > NOTE: cutoff dates are subject to change. > > May 25, Monday - Cutoff date for requests to schedule Working Group > meetings and for preliminary BOF proposals to ADs at 17:00 PDT (24:00 > UTC/GMT). > June 8, Monday - Cutoff date for requests to Area Directors to =20 > schedule > BOFs at 17:00 PDT (24:00 UTC/GMT). > June 15, Monday - Cutoff date for Area Directors to approve BOFs at =20= > 17:00 > PDT (24:00 UTC/GMT). > June 19, Friday - Preliminary agenda published for comment. > July 1, Wednesday - Cutoff date for requests to reschedule Working =20 > Group > and BOF meetings 17:00 PDT (24:00 UTC/GMT). > July 6, Monday - Final agenda to be published. > July 15, Wednesday - Draft Working Group agendas due by 17:00 PT =20 > (24:00 > UTC/GMT). > July 20, Monday - Revised Working Group agendas due by 17:00 PT (24:00 > UTC/GMT). > > Submitting Requests for Working Group and BOF Sessions > > Please submit requests to schedule your Working Group sessions using =20= > the > "IETF Meeting Session Request Tool," a Web-based tool for submitting =20= > all > of the information that the Secretariat requires to schedule your > sessions. > > The URL for the tool is: > > https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi > > Instructions for using the tool are available at: > > http://www.ietf.org/instructions/session_request_tool_instruction.html > > Please send requests to schedule your BOF sessions to agenda@ietf.org. > Please include the acronym of your BOF in the subject line of the =20 > message, > and include all of the information specified in item (4) of =20 > "Requesting > Meeting Sessions at IETF Meetings" in the body. (This document is > included below.) > > Submitting Session Agendas > > For the convenience of meeting attendees, we ask that you submit the > agendas for your Working Group sessions as early as possible. Draft > Working Group agendas are due Wednesday, July 15 by 17:00 PDT (24:00 > UTC/GMT). Revised Working Group agendas are due no later than Monday, > July 20 at 17:00 PDT (24:00 UTC/GMT). The proposed agenda for a BOF > session should be submitted along with your request for a session. =20= > Please > be sure to copy your Area Director on that message. > > Please submit the agendas for your Working Group sessions using the =20= > "IETF > Meeting Materials Management Tool," a Web-based tool for making your > meeting agenda, minutes, and presentation slides available to the > community before, during, and after an IETF meeting. If you are a BOF > chair, then you may use the tool to submit a revised agenda as well as > other materials for your BOF once the BOF has been approved. > > The URL for the tool is: > > https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi > > Additional information about this tool is available at: > > http://www.ietf.org/instructions/meeting_materials_tool.html > > Agendas submitted via the tool will be available to the public on the > "IETF Meeting Materials" Web page as soon as they are submitted. > > The URL for the "IETF 75 Meeting Materials" Web page is: > > = https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=3D75= > > If you are a Working Group chair, then you already have accounts on =20= > the > "IETF Meeting Session Request Tool" and the "IETF Meeting Materials > Management Tool." The same User ID and password will work for both =20= > tools. > If you are a BOF chair who is not also a Working Group chair, then =20= > you > will be given an account on the "IETF Meeting Materials Management =20 > Tool" > when your BOF has been approved. If you require assistance in using > either tool, or wish to report a bug, then please send a message to: > ietf-action@ietf.org. > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > For your convenience, comprehensive information on requesting meeting > sessions at IETF 75 is presented below: > > 1. Requests to schedule Working Group sessions should be submitted =20 > using > the "IETF Meeting Session Request Tool," a Web-based tool for =20 > submitting > all of the information required by the Secretariat to schedule your > sessions. The URL for the tool is: > > https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi > > Instructions for using the tool are available at: > > http://www.ietf.org/instructions/session_request_tool_instruction.html > > If you require an account on this tool, or assistance in using it, =20 > then > please send a message to ietf-action@ietf.org. If you are unable to =20= > use > the tool, then you may send your request via e-mail to =20 > agenda@ietf.org, > with a copy to the appropriate Area Director(s). > > Requests to schedule BOF sessions must be sent to agenda@ietf.org =20 > with a > copy to the appropriate Area Director(s). > > When submitting a Working Group or BOF session request by e-mail, =20 > please > include the Working Group or BOF acronym in the Subject line. > > 2. BOFs will NOT be scheduled unless the Area Director(s) approved > request is accompanied by a BOF'S FULL NAME AND ACRONYM, AREA, =20 > CHAIR(S) > NAME(S) (given together with e-mail address(es)), AN AGENDA AND FULL > DESCRIPTION, and the information requested in (4) below. (Please =20 > read the > BOF Procedure at: http://www.ietf.org/ietf/1bof-procedures.txt before > requesting a session for a BOF.) > > 3. A Working Group may request either one or two sessions. If your > Working Group requires more than two sessions, then your request =20 > must be > approved by an Area Director. Additional sessions will be assigned, =20= > based > on availability, after Wednesday, July 1 at 17:00 PDT (24:00 UTC/=20 > GMT), the > cut-off date for requests to reschedule a session. > > 4. You MUST provide the following information before a Working Group =20= > or > BOF session will be scheduled: > > a. Working Group or BOF full name with acronym in brackets: > > b. AREA under which Working Group or BOF appears: > > c. CONFLICTS you wish to avoid, please be as specific as possible: > > d. Expected Attendance (figures from the 74th IETF meeting are > included at the end of this message): > > e. Special requests: > > f. Number of sessions: > > g. Length of session: > - 1 hour > - 1 1/2 hours > - 2 hours > - 2 1/2 hours > > For more information on scheduling Working Group and BOF sessions, =20 > please > refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and =20 > Procedures" > (http://www.ietf.org/rfc/rfc2418.txt). > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > For your convenience please find here a list of the IETF Area =20 > Directors > with their e-mail addresses: > > IETF Chair > Russ Housley > > Applications Area (app) > Lisa Dusseault > Alexey Melnikov > > Internet Area (int) > Jari Arkko > Ralph Droms > > Operations & Management Area (ops) > Ronald Bonica > Dan Romascanu > > Real-time Applications and Infrastructure Area (rai) > Cullen Jennings > Robert Sparks > > Routing Area (rtg) > Ross Callon > Adrian Farrel > > Security Area (sec) > Pasi Eronen > Tim Polk > > Transport Area (tsv) > Lars Eggert > Magnus Westerlund > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 74th IETF Meeting Attendance Number > > 6ai 189 > 6lowpan NO SHEETS > 6man 138 > alto 112 > ancp 21 > apparea 92 > atoca 77 > autoconf 34 > avt 77 > avt (2nd session) 65 > behave 150 > behave (2nd session) 116 > bliss 64 > bmwg 23 > capwap 16 > ccamp 76 > ccamp (2nd session) 55 > csi 16 > dccp 18 > dhc 50 > dime 31 > dkim 46 > dnsop 90 > drinks 69 > dtnrg 44 > ecrit 80 > emu 35 > fecframe 17 > forces 20 > geopriv 68 > grow 75 > hiprg 38 > hokey 40 > httpbis 25 > idnabis 70 > idnabis (2nd session) 41 > idr 127 > intarea 207 > ipfix 32 > ippm 46 > ipsecme 44 > isms 25 > keyprov 24 > kitten 11 > krb-wg 26 > l2vpn 149 > l3vpn 48 > ledbat 30 > lisp 176 > manet 45 > mboned 37 > mediactrl 47 > mext 96 > mif 68 > mip4 35 > mipshop 57 > mmox 77 > mmusic 75 > morg 15 > mpls 144 > mpls (2nd session) 135 > msec 30 > nea 28 > netconf 39 > netext 68 > netmod 25 > netmod (2nd session) 32 > nfsv4 22 > nsis 23 > oauth 105 > opsarea 86 > opsec 24 > ospf 34 > p2prg 99 > p2psip 71 > pce 63 > pcn 24 > pim 41 > pkix 50 > pmol 27 > pre8prob 44 > pwe3 115 > radext 19 > rtgarea 122 > rmt 12 > roll 69 > rrg 106 > rtgwg 112 > saag 116 > sasl 24 > savi 60 > shara 155 > sidr 77 > sieve 17 > simple 69 > sip 126 > sip (2nd session) 117 > sipping 92 > softwire 73 > speermint 63 > storm 14 > tcpm 33 > tcpm (2nd session) 59 > tictoc 37 > tls 44 > trill 55 > tsvarea 72 > tsvwg 47 > v6ops 126 > v6ops (second session) 65 > vcarddav 18 > xcon 48 > xmpp2 86 > yam 41 >