draft-ietf-6man-multicast-addr-arch-update: How to implement RFCs changes?
<mohamed.boucadair@orange.com> Thu, 23 May 2013 08:16 UTC
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A648221F8FB3 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 01:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level:
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
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 1bVW2cmXvwx2 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 01:16:51 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id D3D8921F9060 for <ipv6@ietf.org>; Thu, 23 May 2013 01:16:26 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id C975722CD7D for <ipv6@ietf.org>; Thu, 23 May 2013 10:16:18 +0200 (CEST)
Received: from puexch31.nanterre.francetelecom.fr (unknown [10.101.44.29]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id A76B227C06A for <ipv6@ietf.org>; Thu, 23 May 2013 10:16:18 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by puexch31.nanterre.francetelecom.fr ([10.101.44.29]) with mapi; Thu, 23 May 2013 10:16:18 +0200
From: mohamed.boucadair@orange.com
To: "ipv6@ietf.org" <ipv6@ietf.org>
Date: Thu, 23 May 2013 10:16:17 +0200
Subject: draft-ietf-6man-multicast-addr-arch-update: How to implement RFCs changes?
Thread-Topic: draft-ietf-6man-multicast-addr-arch-update: How to implement RFCs changes?
Thread-Index: Ac5Xjclm8D6IaijwSZajdqJAw0SrUA==
Message-ID: <94C682931C08B048B7A8645303FDC9F36ED1F52610@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.5.21.113319
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 08:17:01 -0000
Dear all, We prepared a new version which lists the changes to be added to RFC 3956, RFC 3306 and RFC 4607: http://tools.ietf.org/html/draft-ietf-6man-multicast-addr-arch-update-01 We are interested to hear your feedback on the proposed changes and also on the better approach to actually do the changes. We have considered two approaches: (1) maintain all the changes in this document (i.e., it will update the address architecture + RFC 3956, RFC 3306 and RFC 4607) (2) this document updates only the address architecture with the new flag + edit bis documents which will update RFC 3956, RFC 3306 and RFC 4607. What approach the WG want us to implement? Comments are more than welcome. Cheers, Med >-----Message d'origine----- >De : ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] De la part de >internet-drafts@ietf.org >Envoyé : jeudi 23 mai 2013 10:02 >À : i-d-announce@ietf.org >Cc : ipv6@ietf.org >Objet : I-D Action: draft-ietf-6man-multicast-addr-arch-update-01.txt > > >A New Internet-Draft is available from the on-line Internet-Drafts >directories. > This draft is a work item of the IPv6 Maintenance Working Group of the >IETF. > > Title : Updates to the IPv6 Multicast Addressing >Architecture > Author(s) : Mohamed Boucadair > Stig Venaas > Filename : draft-ietf-6man-multicast-addr-arch-update-01.txt > Pages : 10 > Date : 2013-05-23 > >Abstract: > This document updates the IPv6 multicast addressing architecture by > defining the 17-20 reserved bits as generic flag bits. The document > provides also some clarifications related to the use of these flag > bits. > > This document updates RFC 3956, RFC 3306, RFC 4607 and RFC 4291. > > > >The IETF datatracker status page for this draft is: >https://datatracker.ietf.org/doc/draft-ietf-6man-multicast-addr-arch-update > >There's also a htmlized version available at: >http://tools.ietf.org/html/draft-ietf-6man-multicast-addr-arch-update-01 > >A diff from the previous version is available at: >http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-multicast-addr-arch- >update-01 > > >Internet-Drafts are also available by anonymous FTP at: >ftp://ftp.ietf.org/internet-drafts/ > >-------------------------------------------------------------------- >IETF IPv6 working group mailing list >ipv6@ietf.org >Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 >--------------------------------------------------------------------
- draft-ietf-6man-multicast-addr-arch-update: How t… mohamed.boucadair