Re: [Idr] draft-rosen-idr-extcomm-iana-00.txt

[<[e-mail]>]

Hi Sue, John, all,

I've read and support WG adoption.

Bruno

>-----Original Message-----
>From: [e-mail] [mailto:[e-mail]] On Behalf Of Susan
>Hares
>Sent: Monday, June 24, 2013 8:24 PM
>To: 'Yakov Rekhter'; [e-mail]
>Cc: [e-mail]; [e-mail]
>Subject: Re: [Idr] draft-rosen-idr-extcomm-iana-00.txt
>
>Yakov and John:
>
>I've not seen John's official call for the acceptance of this draft as
>WG-Draft.  We will extend this call until 7/5/13.
>
>Sue Hares
>
>-----Original Message-----
>From: Yakov Rekhter [mailto:[e-mail]]
>Sent: Wednesday, June 12, 2013 10:34 AM
>To: [e-mail]; Susan Hares
>Cc: [e-mail]; [e-mail]
>Subject: [Idr] draft-rosen-idr-extcomm-iana-00.txt
>
>Sue and John,
>
>The authors of draft-rosen-idr-extcomm-iana-00.txt would like the IDR WG to
>accept this draft as an IDR WG document.
>
>Yakov & Eric.
>------- Forwarded Message
>
>Date:    Fri, 31 May 2013 11:47:38 -0400
>From:    Eric Rosen <[e-mail]>
>To:      IDR WG <[e-mail]>
>Subject: [Idr] draft-rosen-idr-extcomm-iana-00.txt
>
>- --=-=-=
>Content-Type: text/plain
>
>I would like to call this draft to the attention of the WG.
>
>This draft proposes to reorganize the IANA registries for BGP Extended
>Communities, so that there are separate registries for types and sub-types,
>and so that the values that are available for assignment in one registry do
>not depend upon the values that have already been assigned in another.
>
>Yakov and I put this proposal together after hearing some complaints from
>IANA about the difficulty of figuring out which values are available in
>which registries.  We also found some mistakes in the registries and some
>inconsistencies in the drafts that define the registries.  The intention of
>this draft is to make it easier for IANA to fulfill its clerical function,
>and to make it easier to understand what to request of IANA when a new
>Extended Community is defined.  No changes to existing implementations or
>deployments are required.
>
>If you care about this sort of stuff, please review and provide your
>comments.
>
>
>
>- --=-=-=
>Content-Type: message/rfc822
>Content-Disposition: inline; filename=3423
>Content-Description: forwarded message
>
>MIME-Version: 1.0
>Received: from mail.cisco.com [173.37.183.72]
>	by erosen-linux with IMAP (fetchmail-6.3.6)
>	for <erosen@localhost> (single-drop); Thu, 30 May 2013 13:51:50
>-0400 (
>EDT)
>Received: from rcdn-iport-3.cisco.com (173.37.86.74) by mail.cisco.com
> (173.36.12.79) with Microsoft SMTP Server (TLS) id 14.2.318.4; Thu, 30 May
> 2013 12:51:06 -0500
>Received: from rcdn-core-3.cisco.com ([173.37.93.154])  by
>rcdn-iport-3.cisco.com with ESMTP; 30 May 2013 17:51:06 +0000
>Received: from rcdn-inbound-h.cisco.com (rcdn-inbound-h.cisco.com
> [72.163.7.177])	by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP
>id
> r4UHp50T018972;	Thu, 30 May 2013 17:51:05 GMT
>Authentication-Results: rcdn-inbound-h.cisco.com; dkim=pass (signature
>verified
> [TEST]) header.i=@ietf.org
>X-from-outside-Cisco: 12.22.58.30
>X-IronPort-Anti-Spam-Filtered: true
>X-IronPort-Anti-Spam-Result:
>AiwBAMCQp1EMFjoenGdsb2JhbABZgmhRjG22JxYOAQEBAQEGDQ
>kJFCiCJQEBBAEBNwYBAQQKHgwCAwECBgJACAgDASNJBQSIBQIJqFCEPgEFjkoGjzmDQYkjik2DUA
>GBK
>Yp3hEKEDQ
>X-IronPort-AV: E=Sophos;i="4.87,772,1363132800";
>   d="scan'208";a="108541937"
>Received: from mail.ietf.org ([12.22.58.30])  by rcdn-inbound-h.cisco.com
>with  ESMTP; 30 May 2013 17:51:02 +0000
>Received: from ietfa.amsl.com (localhost [IPv6:::1])	by ietfa.amsl.com
> (Postfix) with ESMTP id EC2E521F968F;	Thu, 30 May 2013 10:50:53 -0700
>(PDT)
>DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
>	t=1369936254; bh=f9K8hgMBlrC6IvJlZGQ7gsMdJ1y8H9QLf1OKoW85G7s=;
>	h=MIME-Version:From:To:Subject:Message-ID:Date:Reply-To:List-Id:
>	 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
>	 Content-Type:Content-Transfer-Encoding:Sender;
>	b=OVexJgUO33kxYqNt/rg6+OrLmO1a2+GxCT13wCvsmy3Pm41a2DfP7BKhFbwdocfzE
>	 PGEjASzZW82rK5JwD/dI59+Byy9b13OLAN/U6q48AApj52j4T0/LrM22gJw89RXKcc
>	 llbJsjQFt0J6nZEn99e+BEszFZa7emUMWv8s2npY=
>X-Original-To: [e-mail]
>Delivered-To: [e-mail]
>Received: from localhost (localhost [127.0.0.1])	by ietfa.amsl.com
>(Post
>fix)
> with ESMTP id 7792021F968D	for <[e-mail]>; Thu, 30
>May
> 2013 10:50:49 -0700 (PDT)
>X-Virus-Scanned: amavisd-new at amsl.com
>X-Spam-Flag: NO
>X-Spam-Score: -102.521
>X-Spam-Level:
>X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5
>	tests=[AWL=0.079, BAYES_00=-2.599, NO_RELAYS=-0.001,
>	USER_IN_WHITELIST=-100]
>Received: from mail.ietf.org ([12.22.58.30])	by localhost (ietfa.amsl.com
> [127.0.0.1]) (amavisd-new, port 10024)	with ESMTP id H1yYnbYGT9sp for
> <[e-mail]>;	Thu, 30 May 2013 10:50:48 -0700 (PDT)
>Received: from ietfa.amsl.com (localhost [IPv6:::1])	by ietfa.amsl.com
> (Postfix) with ESMTP id 4A9AE21F9413	for <[e-mail]>; Thu,
>30
>Ma
>y
> 2013 10:50:46 -0700 (PDT)
>From: <[e-mail]>
>To: <[e-mail]>
>Subject: I-D Action: draft-rosen-idr-extcomm-iana-00.txt
>X-Test-IDTracker: no
>X-IETF-IDTracker: 4.50
>Message-ID: <[e-mail]>
>Date: Thu, 30 May 2013 10:50:46 -0700
>X-BeenThere: [e-mail]
>X-Mailman-Version: 2.1.12
>Precedence: list
>Reply-To: <[e-mail]>
>List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
>List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>,
>	<mailto:[e-mail]?subject=unsubscribe>
>List-Archive: <http://www.ietf.org/mail-archive/web/i-d-announce>
>List-Post: <mailto:[e-mail]>
>List-Help: <mailto:[e-mail]?subject=help>
>List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
>	<mailto:[e-mail]?subject=subscribe>
>Content-Type: text/plain; charset="us-ascii"
>Content-Transfer-Encoding: 7bit
>Sender: <[e-mail]>
>Errors-To: [e-mail]
>Return-Path: [e-mail]
>X-MS-Exchange-Organization-AuthSource: xhc-aln-x05.cisco.com
>X-MS-Exchange-Organization-AuthAs: Internal
>X-MS-Exchange-Organization-AuthMechanism: 10
>
>
>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
>
>
>	Title           : IANA Registries for BGP Extended Communities
>	Author(s)       : Eric C. Rosen
>                          Yakov Rekhter
>	Filename        : draft-rosen-idr-extcomm-iana-00.txt
>	Pages           : 17
>	Date            : 2013-05-30
>
>Abstract:
>   This document reorganizes the IANA Registries for the type values and
>   sub-type values of BGP Extended Communities attribute and the BGP
>   IPv6-Address-Specific Extended Communities attribute.  This is done
>   in order to remove inter-dependencies among the registries, thus
>   making it easier for IANA to determine which codepoints are available
>   for assignment in which registries.  This document also clarifies the
>   information that must be provided to IANA when requesting an
>   allocation from one or more of these registries.  These changes are
>   compatible with the existing allocations, and thus do not affect
>   protocol implementations.  The changes will however impact the "IANA
>   Considerations" sections of future protocol specifications.  This
>   document updates RFCs 4360 and 5701.
>
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-rosen-idr-extcomm-iana
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-rosen-idr-extcomm-iana-00
>
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>I-D-Announce mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/i-d-announce
>Internet-Draft directories: http://www.ietf.org/shadow.html or
>ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>- --=-=-=
>Content-Type: text/plain; charset="us-ascii"
>MIME-Version: 1.0
>Content-Transfer-Encoding: 7bit
>Content-Disposition: inline
>
>_______________________________________________
>Idr mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/idr
>
>- --=-=-=--
>
>------- End of Forwarded Message
>
>
>
>_______________________________________________
>Idr mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/idr

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.