Re: draft-ietf-mboned-64-multicast-address-format
Marshall Eubanks <marshall.eubanks@gmail.com> Fri, 04 May 2012 23:29 UTC
Return-Path: <marshall.eubanks@gmail.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 C17D421E8015; Fri, 4 May 2012 16:29:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.652
X-Spam-Level:
X-Spam-Status: No, score=-103.652 tagged_above=-999 required=5 tests=[AWL=-0.053, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 oSqckSr3S7YF; Fri, 4 May 2012 16:29:59 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9499611E8072; Fri, 4 May 2012 16:29:58 -0700 (PDT)
Received: by lagj5 with SMTP id j5so2728720lag.31 for <multiple recipients>; Fri, 04 May 2012 16:29:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=vgU+/flsSc2TBEBK22njkivnkzYQ2NAX1wijY4CQ13o=; b=eLDeWSsVKrTcQVcp6ZucIG+4lxUp0/QyurBpYrXJssulGVKTOzx/r7ZiVMfFY/QVcn msOGSYQECS4q8tNmkK0RHTErUypfPI3XeGre1PZloqEbRFXkbhIC3ua25eO7BMF9LnrE tZeZGsMYjEKcNs5757cEYuXKVLKV17QrpUrcS6MyEP5URDCwSXqXUlpjAPhXVRMA9h3B VVwM5fm7q06zOPAjwKL+Zuyt8VaUGl6GWgvRBcX7sPOZvhx8SsGmwhwrQ7JYwXJk2jca MFAqstdOorbg/oTkDzcgPK5JjYVZUo1NwsczxG+AIK45OStwgnZYbKQDejV/gs9n1Qqs Q5lA==
MIME-Version: 1.0
Received: by 10.112.37.164 with SMTP id z4mr1846936lbj.100.1336174197452; Fri, 04 May 2012 16:29:57 -0700 (PDT)
Received: by 10.112.56.13 with HTTP; Fri, 4 May 2012 16:29:57 -0700 (PDT)
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE02BB8BA441@XCH-MW-08V.mw.nos.boeing.com>
References: <94C682931C08B048B7A8645303FDC9F36E299468D7@PUEXCB1B.nanterre.francetelecom.fr> <B0147C3DD45E42478038FC347CCB65FE02BB8BA441@XCH-MW-08V.mw.nos.boeing.com>
Date: Fri, 04 May 2012 19:29:57 -0400
Message-ID: <CAJNg7VJzZUnYAtvPB0axBHC6Pwfqtu1SrppE9Ffrmw27Wj4HYQ@mail.gmail.com>
Subject: Re: draft-ietf-mboned-64-multicast-address-format
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "mboned-chairs@ietf.org" <mboned-chairs@ietf.org>, "draft-ietf-mboned-64-multicast-address-format@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format@tools.ietf.org>
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: Fri, 04 May 2012 23:29:59 -0000
On Fri, May 4, 2012 at 3:29 PM, Manfredi, Albert E <albert.e.manfredi@boeing.com> wrote: > I don’t know why IPv6 becomes more arcane with every new I-D. Why not work > to make it simpler, rather than more complex and confusing, with every new > iteration? > When you start with simplicity, experience will add complexity. Regards Marshall > > > In this particular case, it is really confusing to change the location of > this new field, 64IX, depending whether it’s ASM or SSM. And I might suggest > to drop the 64IX nibble altogether. Use the remaining bit of the flgs field > instead of the M bit of the 64IX field, and then allow for different > combinations of the flgs bits for future codes? > > > > Bert > > > > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of > mohamed.boucadair@orange.com > Sent: Friday, May 04, 2012 8:50 AM > To: mboned-chairs@ietf.org; ipv6@ietf.org > Cc: Brian Haberman; > draft-ietf-mboned-64-multicast-address-format@tools.ietf.org > Subject: draft-ietf-mboned-64-multicast-address-format > > > > Dear all, > > > > During the IETF LC for draft-ietf-mboned-64-multicast-address-format, Brian > suggested to use the remaining flag instead of reserving ff3x:0:8000/33 > (SSM) and ffxx:8000/17 (ASM) blocks. FYI, we have considered that approach > in an early version of the document but it has been abandoned because of > comments we received at that time. We recorded the rationale behind our > design choice in: > > http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-01#appendix-A.2. > > > > We are seeking more feedback from 6man and mboned on the following: > > > > (1) Should we maintain the current design choice > > (2) Or adopt the suggestion from Brian? > > > > FWIW, discussion related to this issue can be found here: > http://www.ietf.org/mail-archive/web/mboned/current/msg01508.html. > > The latest version of the draft is available at: > http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-01 > > > > Your help is appreciated. > > > > Cheers, > > Med > > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- >
- draft-ietf-mboned-64-multicast-address-format mohamed.boucadair
- RE: draft-ietf-mboned-64-multicast-address-format Manfredi, Albert E
- Re: draft-ietf-mboned-64-multicast-address-format Marshall Eubanks
- Re: draft-ietf-mboned-64-multicast-address-format Bob Hinden
- Re: draft-ietf-mboned-64-multicast-address-format Tom Taylor
- Re: draft-ietf-mboned-64-multicast-address-format Marshall Eubanks
- RE: draft-ietf-mboned-64-multicast-address-format mohamed.boucadair
- Re: draft-ietf-mboned-64-multicast-address-format Bob Hinden
- RE: draft-ietf-mboned-64-multicast-address-format mohamed.boucadair
- Re: draft-ietf-mboned-64-multicast-address-format Bob Hinden
- Re: draft-ietf-mboned-64-multicast-address-format Jon Steen
- Re: draft-ietf-mboned-64-multicast-address-format Tom Taylor
- draft-ietf-mboned-64-multicast-address-format mohamed.boucadair
- Re: draft-ietf-mboned-64-multicast-address-format Bob Hinden
- Re: draft-ietf-mboned-64-multicast-address-format Behcet Sarikaya
- Re: draft-ietf-mboned-64-multicast-address-format Stig Venaas
- RE: draft-ietf-mboned-64-multicast-address-format mohamed.boucadair
- RE: draft-ietf-mboned-64-multicast-address-format mohamed.boucadair
- RE: draft-ietf-mboned-64-multicast-address-format mohamed.boucadair