
From rbonica@juniper.net  Wed Aug  8 09:16:05 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F345E21F8701 for <mboned@ietfa.amsl.com>; Wed,  8 Aug 2012 09:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.56
X-Spam-Level: 
X-Spam-Status: No, score=-106.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 d9B-NTd3SaDP for <mboned@ietfa.amsl.com>; Wed,  8 Aug 2012 09:16:04 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 1D75C21F8629 for <mboned@ietf.org>; Wed,  8 Aug 2012 09:16:03 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKUCKQwpqOXQT8iX81gZaP/QiStJ+Uy1fW@postini.com; Wed, 08 Aug 2012 09:16:04 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 8 Aug 2012 09:08:09 -0700
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 8 Aug 2012 09:08:08 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Wed, 8 Aug 2012 12:07:47 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "mboned@ietf.org" <mboned@ietf.org>
Date: Wed, 8 Aug 2012 12:07:46 -0400
Thread-Topic: MLTRANS work and draft-ietf-mboned-v4v6-mcast-ps
Thread-Index: Ac11f/MC01wgs+sBTC6coge8PLGVsQ==
Message-ID: <13205C286662DE4387D9AF3AC30EF456D77189AFEB@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [MBONED] MLTRANS work and draft-ietf-mboned-v4v6-mcast-ps
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 16:16:05 -0000

Folks,

All of the MLTRANS work, and in particular, the MLTRANS addressing work, se=
ems to be in a holding pattern waiting for consensus around draft-ietf-mbon=
ed-v4v6-mcast-ps. In order to reach consensus, we need to determine which u=
se cases are likely to see deployment.

Could someone associated with the MLTRANS work be willing to bring draft-ie=
tf-mboned-v4v6-mcast-ps to the attention of the NANOG and RIPE mailing list=
s so that we can get feedback from the larger operational community? This f=
eedback will inform our next step.

In Vancouver, somebody offered to do this, but I can't remember who.

--------------------------
Ron Bonica
vcard:       www.bonica.org/ron/ronbonica.vcf



From tom.taylor.stds@gmail.com  Thu Aug  9 16:32:38 2012
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B24421F8672 for <mboned@ietfa.amsl.com>; Thu,  9 Aug 2012 16:32:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 UDhv3x-U1fJZ for <mboned@ietfa.amsl.com>; Thu,  9 Aug 2012 16:32:37 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id E1AB121F8667 for <mboned@ietf.org>; Thu,  9 Aug 2012 16:32:30 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so1665427pbb.31 for <mboned@ietf.org>; Thu, 09 Aug 2012 16:32:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding:x-antivirus :x-antivirus-status; bh=2j39qPgQwU1eZsFniNuC3k1XrDNB9/29bhkeAIk/Y6k=; b=QfwaE2Nn4DMsDeRC3SAO7Ix0JNnKXQ+0s/Wdk1pK3T5ie3uSJRIr0mAVeZluhd4Bzn fhN0bBwMNtKRV1lxN4vqSAUZ3ktIwmmPVKVKn50wkN9i/CvPHcCFTD45Xa+cAtTwwOTn DA04NkluwrKOnwF5GgZh00W86d1nLO/xs7C+5O91Wfq99HYuuuFNoQPWQyDfAzwQ4i7U RYkFeGxb6KwX5B8lR+RjAPyD0M06dSFli8MalAu4eF5shw2nuMvsqzmhATqVlWNxXPj/ smWSQueQuMWYGwHWSEP+GW4C98WF9h/zjW8a4gv3u5So3d/s7Aqdox9Qg41E2O/A4A1G WFxg==
Received: by 10.68.231.163 with SMTP id th3mr7718553pbc.55.1344555150624; Thu, 09 Aug 2012 16:32:30 -0700 (PDT)
Received: from [127.0.0.1] ([199.246.39.165]) by mx.google.com with ESMTPS id rx7sm2015144pbc.64.2012.08.09.16.32.28 (version=SSLv3 cipher=OTHER); Thu, 09 Aug 2012 16:32:29 -0700 (PDT)
Message-ID: <50244888.6070402@gmail.com>
Date: Thu, 09 Aug 2012 19:32:24 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: mboned@ietf.org
References: <13205C286662DE4387D9AF3AC30EF456D77189AFEB@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D77189AFEB@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120809-0, 09/08/2012), Outbound message
X-Antivirus-Status: Clean
Subject: Re: [MBONED] MLTRANS work and draft-ietf-mboned-v4v6-mcast-ps
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Aug 2012 23:32:38 -0000

For the record, I sent the following E-mail to the NANOG list, and will
send it to others as I track them down:

Subject: IPTV, Multicast, and IPv6 Transition

This may be way off in the future for some of you, or others may be past 
it. In support of possible work on IPv6 transition in the IETF MBONED 
Working Group, I'm looking for an indication of what use cases are 
realistic for operators who:

-- deliver IPTV to their customers
-- use multicast for the purpose, either now or in the near future
-- are making the transition from IPv4 to IPv6.

First question: does anyone anticipate a situation where you will have 
to translate multicast content from an IPv4-only source so it can be 
delivered to an IPv6-only receiver, or vice versa?

Second question: the current official view is that dual stack is the 
sensible way to transition your network, and failing that, you can use 
Automatic Multicast Tunneling, an almost-ready Internet Draft available at

     http://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast/

to tunnel multicast packets through a single-stack network when 
necessary. Do you consider your requirements adequately addressed by 
this view?

People who really want to be helpful can comment on the problem 
statement and use cases documented in

     http://datatracker.ietf.org/doc/draft-ietf-mboned-v4v6-mcast-ps/

Thanks for your attention. Privacy will be respected if people want to 
reply privately.

Tom Taylor
Consultant


On 08/08/2012 12:07 PM, Ronald Bonica wrote:
> Folks,
>
> All of the MLTRANS work, and in particular, the MLTRANS addressing
> work, seems to be in a holding pattern waiting for consensus around
> draft-ietf-mboned-v4v6-mcast-ps. In order to reach consensus, we need
> to determine which use cases are likely to see deployment.
>
> Could someone associated with the MLTRANS work be willing to bring
> draft-ietf-mboned-v4v6-mcast-ps to the attention of the NANOG and
> RIPE mailing lists so that we can get feedback from the larger
> operational community? This feedback will inform our next step.
>
> In Vancouver, somebody offered to do this, but I can't remember who.
>
> -------------------------- Ron Bonica vcard:
> www.bonica.org/ron/ronbonica.vcf
>
>
> _______________________________________________ MBONED mailing list
> MBONED@ietf.org https://www.ietf.org/mailman/listinfo/mboned
>

From internet-drafts@ietf.org  Thu Aug  9 23:49:27 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5573721F8621; Thu,  9 Aug 2012 23:49:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level: 
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, 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 Hvy9RwnNy8s4; Thu,  9 Aug 2012 23:49:26 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CFFF21F85E1; Thu,  9 Aug 2012 23:49:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.33
Message-ID: <20120810064908.22316.70512.idtracker@ietfa.amsl.com>
Date: Thu, 09 Aug 2012 23:49:08 -0700
Cc: mboned@ietf.org
Subject: [MBONED] I-D Action: draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Aug 2012 06:49:27 -0000

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 IET=
F.

	Title           : IPv6 Multicast Address With Embedded IPv4 Multicast Addr=
ess
	Author(s)       : Mohamed Boucadair
                          Jacni Qin
                          Yiu L. Lee
                          Stig Venaas
                          Xing Li
                          Mingwei Xu
	Filename        : draft-ietf-mboned-64-multicast-address-format-03.txt
	Pages           : 13
	Date            : 2012-08-09

Abstract:
   This document reserves two IPv6 multicast prefixes to be used in the
   context of IPv4-IPv6 interconnection.  The document specifies an
   algorithmic translation of an IPv6 multicast address to a
   corresponding IPv4 multicast address, and vice versa.  This
   algorithmic translation can be used in both IPv4-IPv6 translation or
   encapsulation schemes.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast-address-for=
mat

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mboned-64-multicast-address-f=
ormat-03


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


From sarikaya2012@gmail.com  Mon Aug 13 13:21:30 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F9A321F863B for <mboned@ietfa.amsl.com>; Mon, 13 Aug 2012 13:21:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.559
X-Spam-Level: 
X-Spam-Status: No, score=-3.559 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 NplLvk8UK+Gw for <mboned@ietfa.amsl.com>; Mon, 13 Aug 2012 13:21:30 -0700 (PDT)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9495121F84E4 for <mboned@ietf.org>; Mon, 13 Aug 2012 13:21:27 -0700 (PDT)
Received: by qadz3 with SMTP id z3so1436184qad.10 for <mboned@ietf.org>; Mon, 13 Aug 2012 13:21:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=WxRVnno3iGhINIC1RgMIAUZQKiyLh+7+QKVZOh24I8o=; b=A6g9L/SCrTBsQl5V2g/9HsXtoT1sw3Gpg+SL569LyfLj36G6zJbbNIcfv2uWRBTS/v Q9aWCvxQS3kF6/eKEiCP/5f76QdnYr4euXGSlhSCBKlLBl2QqyTDAi22HJ8wX48humgY alY+kezb10PyHqVc6He+OUb/Kcf+UoZlztaxGJ+hemDSG/qZKo20Y3FhzNty94AkVwpp jUEkatwpoDes1y/qHEmDgLOmaFakd75Hdz+Udrxzfe/AlIFOFnzv50Gr5FsgvDfS/VY6 HuURJaO2dTqc9uSAcZqcqvefTfpkKjsQ1+Rb6TwWOc8zBcoVSBXvZJlasSKsXbYUaDOn RS1Q==
MIME-Version: 1.0
Received: by 10.50.94.135 with SMTP id dc7mr7246414igb.37.1344889286776; Mon, 13 Aug 2012 13:21:26 -0700 (PDT)
Received: by 10.231.55.70 with HTTP; Mon, 13 Aug 2012 13:21:26 -0700 (PDT)
Date: Mon, 13 Aug 2012 15:21:26 -0500
Message-ID: <CAC8QAcdJ-u_XrWQ=soNL9rMykMD4W4oxsZrGDBdFcMU8t2ebqg@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: MBONED WG <mboned@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 20:21:30 -0000

Hi authors,

Thanks for the revised draft, I find that the revision is in the right
direction.

I am confused on the prefix lengths:
on Figure 2,
ffxx:8000:0:abc::/96
while in Section 3.1
ffxx:8000::/20

How come these are reserved prefixes?
What are the values that are reserved?

If you look at RFC 6052, the unicast translation specification,
64:ff9b::/96 is defined as the Well-Known Prefix. There are no x's in
the prefix definition.

Regards,

Behcet

On Fri, Aug 10, 2012 at 1:49 AM,  <internet-drafts@ietf.org> wrote:
>
> 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           : IPv6 Multicast Address With Embedded IPv4 Multicast Address
>         Author(s)       : Mohamed Boucadair
>                           Jacni Qin
>                           Yiu L. Lee
>                           Stig Venaas
>                           Xing Li
>                           Mingwei Xu
>         Filename        : draft-ietf-mboned-64-multicast-address-format-03.txt
>         Pages           : 13
>         Date            : 2012-08-09
>
> Abstract:
>    This document reserves two IPv6 multicast prefixes to be used in the
>    context of IPv4-IPv6 interconnection.  The document specifies an
>    algorithmic translation of an IPv6 multicast address to a
>    corresponding IPv4 multicast address, and vice versa.  This
>    algorithmic translation can be used in both IPv4-IPv6 translation or
>    encapsulation schemes.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast-address-format
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-03
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-64-multicast-address-format-03
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From brian@innovationslab.net  Mon Aug 13 14:46:39 2012
Return-Path: <brian@innovationslab.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF90E21F84F5 for <mboned@ietfa.amsl.com>; Mon, 13 Aug 2012 14:46:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 GL26Mgx50VwR for <mboned@ietfa.amsl.com>; Mon, 13 Aug 2012 14:46:38 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id DD03E21F8645 for <mboned@ietf.org>; Mon, 13 Aug 2012 14:46:35 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id C75C088093 for <mboned@ietf.org>; Mon, 13 Aug 2012 14:46:35 -0700 (PDT)
Received: from Littlejohn.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 657D9130017 for <mboned@ietf.org>; Mon, 13 Aug 2012 14:46:35 -0700 (PDT)
Message-ID: <502975B9.30403@innovationslab.net>
Date: Mon, 13 Aug 2012 17:46:33 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: mboned@ietf.org
References: <CAC8QAcdJ-u_XrWQ=soNL9rMykMD4W4oxsZrGDBdFcMU8t2ebqg@mail.gmail.com>
In-Reply-To: <CAC8QAcdJ-u_XrWQ=soNL9rMykMD4W4oxsZrGDBdFcMU8t2ebqg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 21:46:39 -0000

On 8/13/12 4:21 PM, Behcet Sarikaya wrote:
> Hi authors,
>
> Thanks for the revised draft, I find that the revision is in the right
> direction.
>
> I am confused on the prefix lengths:
> on Figure 2,
> ffxx:8000:0:abc::/96
> while in Section 3.1
> ffxx:8000::/20
>

The x's correspond to the flags and scope fields within the multicast 
address.  Take a look at:

http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-addresses.xml#ipv6-multicast-addresses-4


> How come these are reserved prefixes?
> What are the values that are reserved?
>
> If you look at RFC 6052, the unicast translation specification,
> 64:ff9b::/96 is defined as the Well-Known Prefix. There are no x's in
> the prefix definition.
>
> Regards,
>
> Behcet
>
> On Fri, Aug 10, 2012 at 1:49 AM,  <internet-drafts@ietf.org> wrote:
>>
>> 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           : IPv6 Multicast Address With Embedded IPv4 Multicast Address
>>          Author(s)       : Mohamed Boucadair
>>                            Jacni Qin
>>                            Yiu L. Lee
>>                            Stig Venaas
>>                            Xing Li
>>                            Mingwei Xu
>>          Filename        : draft-ietf-mboned-64-multicast-address-format-03.txt
>>          Pages           : 13
>>          Date            : 2012-08-09
>>
>> Abstract:
>>     This document reserves two IPv6 multicast prefixes to be used in the
>>     context of IPv4-IPv6 interconnection.  The document specifies an
>>     algorithmic translation of an IPv6 multicast address to a
>>     corresponding IPv4 multicast address, and vice versa.  This
>>     algorithmic translation can be used in both IPv4-IPv6 translation or
>>     encapsulation schemes.
>>
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast-address-format
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-03
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-64-multicast-address-format-03
>>
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> MBONED mailing list
>> MBONED@ietf.org
>> https://www.ietf.org/mailman/listinfo/mboned
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>



From stig@venaas.com  Mon Aug 13 16:17:23 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 658C521F849C for <mboned@ietfa.amsl.com>; Mon, 13 Aug 2012 16:17:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 39nPGPmQchdu for <mboned@ietfa.amsl.com>; Mon, 13 Aug 2012 16:17:22 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 3B71B21F84D1 for <mboned@ietf.org>; Mon, 13 Aug 2012 16:17:22 -0700 (PDT)
Received: from [10.21.144.1] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id A0F207FCD; Tue, 14 Aug 2012 01:17:19 +0200 (CEST)
Message-ID: <50298B3E.2020207@venaas.com>
Date: Mon, 13 Aug 2012 16:18:22 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
References: <CAC8QAcdJ-u_XrWQ=soNL9rMykMD4W4oxsZrGDBdFcMU8t2ebqg@mail.gmail.com> <502975B9.30403@innovationslab.net>
In-Reply-To: <502975B9.30403@innovationslab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mboned@ietf.org
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Aug 2012 23:17:23 -0000

On 13.08.2012 14:46, Brian Haberman wrote:
> On 8/13/12 4:21 PM, Behcet Sarikaya wrote:
>> Hi authors,
>>
>> Thanks for the revised draft, I find that the revision is in the right
>> direction.
>>
>> I am confused on the prefix lengths:
>> on Figure 2,
>> ffxx:8000:0:abc::/96
>> while in Section 3.1
>> ffxx:8000::/20
>>
>
> The x's correspond to the flags and scope fields within the multicast
> address.  Take a look at:
>
> http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-addresses.xml#ipv6-multicast-addresses-4

We have one minor issue here though. They cannot simply be IANA
allocations, since they would not have the transient bit set. In
this case, the idea is that it should work for flag nibble values
like 1, 3 and 7. Actually I believe the transient bit should always
be set for these groups.

Stig

>
>
>> How come these are reserved prefixes?
>> What are the values that are reserved?
>>
>> If you look at RFC 6052, the unicast translation specification,
>> 64:ff9b::/96 is defined as the Well-Known Prefix. There are no x's in
>> the prefix definition.
>>
>> Regards,
>>
>> Behcet
>>
>> On Fri, Aug 10, 2012 at 1:49 AM,  <internet-drafts@ietf.org> wrote:
>>>
>>> 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           : IPv6 Multicast Address With Embedded IPv4
>>> Multicast Address
>>>          Author(s)       : Mohamed Boucadair
>>>                            Jacni Qin
>>>                            Yiu L. Lee
>>>                            Stig Venaas
>>>                            Xing Li
>>>                            Mingwei Xu
>>>          Filename        :
>>> draft-ietf-mboned-64-multicast-address-format-03.txt
>>>          Pages           : 13
>>>          Date            : 2012-08-09
>>>
>>> Abstract:
>>>     This document reserves two IPv6 multicast prefixes to be used in the
>>>     context of IPv4-IPv6 interconnection.  The document specifies an
>>>     algorithmic translation of an IPv6 multicast address to a
>>>     corresponding IPv4 multicast address, and vice versa.  This
>>>     algorithmic translation can be used in both IPv4-IPv6 translation or
>>>     encapsulation schemes.
>>>
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast-address-format
>>>
>>>
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-03
>>>
>>>
>>> A diff from the previous version is available at:
>>> http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-64-multicast-address-format-03
>>>
>>>
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> _______________________________________________
>>> MBONED mailing list
>>> MBONED@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mboned
>> _______________________________________________
>> MBONED mailing list
>> MBONED@ietf.org
>> https://www.ietf.org/mailman/listinfo/mboned
>>
>
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


From mohamed.boucadair@orange.com  Tue Aug 14 00:07:35 2012
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77D0111E80D2 for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 00:07:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.015
X-Spam-Level: 
X-Spam-Status: No, score=-2.015 tagged_above=-999 required=5 tests=[AWL=0.233,  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 L-V58uhcq7bV for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 00:07:35 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 8FDD011E80AE for <mboned@ietf.org>; Tue, 14 Aug 2012 00:07:33 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 5FA9A32435A; Tue, 14 Aug 2012 09:07:32 +0200 (CEST)
Received: from PUEXCH61.nanterre.francetelecom.fr (unknown [10.101.44.32]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 4533027C053; Tue, 14 Aug 2012 09:07:32 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH61.nanterre.francetelecom.fr ([10.101.44.32]) with mapi; Tue, 14 Aug 2012 09:07:15 +0200
From: <mohamed.boucadair@orange.com>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>, MBONED WG <mboned@ietf.org>
Date: Tue, 14 Aug 2012 09:07:14 +0200
Thread-Topic: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
Thread-Index: Ac15kTJXedRjCPn7Q6Ozz+FNISPTXgAV6KIA
Message-ID: <94C682931C08B048B7A8645303FDC9F36E4FC2D858@PUEXCB1B.nanterre.francetelecom.fr>
References: <CAC8QAcdJ-u_XrWQ=soNL9rMykMD4W4oxsZrGDBdFcMU8t2ebqg@mail.gmail.com>
In-Reply-To: <CAC8QAcdJ-u_XrWQ=soNL9rMykMD4W4oxsZrGDBdFcMU8t2ebqg@mail.gmail.com>
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: 2012.8.14.60320
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 07:07:35 -0000

Hi Behcet, all,

I was planning to send an e-mail to the list to notify the main changes we =
implemented in -03. Since you started this thread, I will use it for that p=
urpose.=20

The main changes are as follows:

* Abandon the M-bit idea

* Reserve two prefixes to be used for the algorithmic translation of an IPv=
6 multicast address into an IPv4 one; and vice versa
(1) ff3x:0:8000::/96 for SSM
(2) ffxx:8000::/20 for ASM

* Explain the rationale for selecting a /96 (SSM) and /20 (ASM)

* The document does not update RFC4291; i.e., no change to the IPv6 address=
ing architecture.

Cheers,
Med


>-----Message d'origine-----
>De : mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org]=20
>De la part de Behcet Sarikaya
>Envoy=E9 : lundi 13 ao=FBt 2012 22:21
>=C0 : MBONED WG
>Objet : [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
>
>Hi authors,
>
>Thanks for the revised draft, I find that the revision is in the right
>direction.
>
>I am confused on the prefix lengths:
>on Figure 2,
>ffxx:8000:0:abc::/96
>while in Section 3.1
>ffxx:8000::/20
>
>How come these are reserved prefixes?
>What are the values that are reserved?
>
>If you look at RFC 6052, the unicast translation specification,
>64:ff9b::/96 is defined as the Well-Known Prefix. There are no x's in
>the prefix definition.
>
>Regards,
>
>Behcet
>
>On Fri, Aug 10, 2012 at 1:49 AM,  <internet-drafts@ietf.org> wrote:
>>
>> A New Internet-Draft is available from the on-line=20
>Internet-Drafts directories.
>>  This draft is a work item of the MBONE Deployment Working=20
>Group of the IETF.
>>
>>         Title           : IPv6 Multicast Address With=20
>Embedded IPv4 Multicast Address
>>         Author(s)       : Mohamed Boucadair
>>                           Jacni Qin
>>                           Yiu L. Lee
>>                           Stig Venaas
>>                           Xing Li
>>                           Mingwei Xu
>>         Filename        :=20
>draft-ietf-mboned-64-multicast-address-format-03.txt
>>         Pages           : 13
>>         Date            : 2012-08-09
>>
>> Abstract:
>>    This document reserves two IPv6 multicast prefixes to be=20
>used in the
>>    context of IPv4-IPv6 interconnection.  The document specifies an
>>    algorithmic translation of an IPv6 multicast address to a
>>    corresponding IPv4 multicast address, and vice versa.  This
>>    algorithmic translation can be used in both IPv4-IPv6=20
>translation or
>>    encapsulation schemes.
>>
>>
>>
>> The IETF datatracker status page for this draft is:
>>=20
>https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast
>-address-format
>>
>> There's also a htmlized version available at:
>>=20
>http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-addre
ss-format-03
>>
>> A diff from the previous version is available at:
>>=20
>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mboned-64-multicast
>-address-format-03
>>
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> MBONED mailing list
>> MBONED@ietf.org
>> https://www.ietf.org/mailman/listinfo/mboned
>_______________________________________________
>MBONED mailing list
>MBONED@ietf.org
>https://www.ietf.org/mailman/listinfo/mboned
>=

From sarikaya2012@gmail.com  Tue Aug 14 09:55:00 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A490121F87AA for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 09:55:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.561
X-Spam-Level: 
X-Spam-Status: No, score=-3.561 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 WJaRmbKE4Czk for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 09:54:59 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id C076E21F87A7 for <mboned@ietf.org>; Tue, 14 Aug 2012 09:54:59 -0700 (PDT)
Received: by qcac10 with SMTP id c10so527401qca.31 for <mboned@ietf.org>; Tue, 14 Aug 2012 09:54:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Fvc0OSHoAjglbOcNGf+/vbVDpB90n6gM9TPzJdtaCt8=; b=CAoB8D9iXgg7z0kcMNAH0OXKUvmP1RscOd3X7ODwti78ANp10DVQL1KtwICru1HCst IDwhTFVYORXUpdOv4KiYmDyonJ0otK9sWeelKPLQLKSRlmXy1h2RuOPCZ6BIgTW7O+gn yRAgbNaiO2h2oV9LDNHMVgiSm2vhVtU5eYHWcODs7eKgVbD8DIm9m3NLJTngxdBt5EcJ rnxsoQ7XY2EJaV6FaFI+1yJiCejqTohebYTSGr0YntAk0dUY7vyRsdUOBdZ0Yva+9l87 Cxs+KyvTP97vl+4eYsWlkCPJ/FoN9O5K2Z+lttt196Mf1wM2h3x98X5LQqHIIUCpLc/m aPjQ==
MIME-Version: 1.0
Received: by 10.50.187.228 with SMTP id fv4mr10373779igc.37.1344963298767; Tue, 14 Aug 2012 09:54:58 -0700 (PDT)
Received: by 10.231.55.70 with HTTP; Tue, 14 Aug 2012 09:54:58 -0700 (PDT)
In-Reply-To: <50298B3E.2020207@venaas.com>
References: <CAC8QAcdJ-u_XrWQ=soNL9rMykMD4W4oxsZrGDBdFcMU8t2ebqg@mail.gmail.com> <502975B9.30403@innovationslab.net> <50298B3E.2020207@venaas.com>
Date: Tue, 14 Aug 2012 11:54:58 -0500
Message-ID: <CAC8QAcc4V3x=AG+XC-bOupkKzyfOTJDR2b=RBiJBgojd7A9LaA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Stig Venaas <stig@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: mboned@ietf.org
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 16:55:00 -0000

On Mon, Aug 13, 2012 at 6:18 PM, Stig Venaas <stig@venaas.com> wrote:
> On 13.08.2012 14:46, Brian Haberman wrote:
>>
>> On 8/13/12 4:21 PM, Behcet Sarikaya wrote:
>>>
>>> Hi authors,
>>>
>>> Thanks for the revised draft, I find that the revision is in the right
>>> direction.
>>>
>>> I am confused on the prefix lengths:
>>> on Figure 2,
>>> ffxx:8000:0:abc::/96
>>> while in Section 3.1
>>> ffxx:8000::/20
>>>
>>
>> The x's correspond to the flags and scope fields within the multicast
>> address.  Take a look at:
>>
>>
>> http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-addresses.xml#ipv6-multicast-addresses-4
>
>
> We have one minor issue here though. They cannot simply be IANA
> allocations, since they would not have the transient bit set. In
> this case, the idea is that it should work for flag nibble values
> like 1, 3 and 7. Actually I believe the transient bit should always
> be set for these groups.

I think it will be better to clarify in the draft saying that xx
corresponds to flgs and scop fields defined in RFC 3306.

Regards,

Behcet

>
> Stig
>
>
>>
>>
>>> How come these are reserved prefixes?
>>> What are the values that are reserved?
>>>
>>> If you look at RFC 6052, the unicast translation specification,
>>> 64:ff9b::/96 is defined as the Well-Known Prefix. There are no x's in
>>> the prefix definition.
>>>
>>> Regards,
>>>
>>> Behcet
>>>
>>> On Fri, Aug 10, 2012 at 1:49 AM,  <internet-drafts@ietf.org> wrote:
>>>>
>>>>
>>>> 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           : IPv6 Multicast Address With Embedded IPv4
>>>> Multicast Address
>>>>          Author(s)       : Mohamed Boucadair
>>>>                            Jacni Qin
>>>>                            Yiu L. Lee
>>>>                            Stig Venaas
>>>>                            Xing Li
>>>>                            Mingwei Xu
>>>>          Filename        :
>>>> draft-ietf-mboned-64-multicast-address-format-03.txt
>>>>          Pages           : 13
>>>>          Date            : 2012-08-09
>>>>
>>>> Abstract:
>>>>     This document reserves two IPv6 multicast prefixes to be used in the
>>>>     context of IPv4-IPv6 interconnection.  The document specifies an
>>>>     algorithmic translation of an IPv6 multicast address to a
>>>>     corresponding IPv4 multicast address, and vice versa.  This
>>>>     algorithmic translation can be used in both IPv4-IPv6 translation or
>>>>     encapsulation schemes.
>>>>
>>>>
>>>>
>>>> The IETF datatracker status page for this draft is:
>>>>
>>>> https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast-address-format
>>>>
>>>>
>>>> There's also a htmlized version available at:
>>>>
>>>> http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-03
>>>>
>>>>
>>>> A diff from the previous version is available at:
>>>>
>>>> http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-64-multicast-address-format-03
>>>>
>>>>
>>>>
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>
>>>> _______________________________________________
>>>> MBONED mailing list
>>>> MBONED@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>
>>> _______________________________________________
>>> MBONED mailing list
>>> MBONED@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mboned
>>>
>>
>>
>> _______________________________________________
>> MBONED mailing list
>> MBONED@ietf.org
>> https://www.ietf.org/mailman/listinfo/mboned
>
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From sarikaya2012@gmail.com  Tue Aug 14 13:05:02 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D86C821E809B for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 13:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.561
X-Spam-Level: 
X-Spam-Status: No, score=-3.561 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 gHt+OsaUTkcB for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 13:05:02 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id F195C21E8063 for <mboned@ietf.org>; Tue, 14 Aug 2012 13:05:01 -0700 (PDT)
Received: by yhq56 with SMTP id 56so992971yhq.31 for <mboned@ietf.org>; Tue, 14 Aug 2012 13:05:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=V0Fh2JQRcXFT8T2r6S+6XiLcseD/Y8VXTv8KMDU52oE=; b=nWrO4ae7GiVZoMbq5Inhp7RG/wpqt0gvPRhxJbUB6+Ii9llvkq+eVO5XgWBSDt6X1E UnNJicuReLvl9wMZ/Ot0IreN2hp8a0RuiKU87dEQlOm8ctLJ32Z1NMEjD3Xnb5BdfVei O23dTQpXoWgE0it5OEr9GcWPyZ2Hi9QApFdCARaMIrgHn+h8YJcqNCoDbEUp0stB8/60 SSGA11sB5xUcXRae1w8bTe3hIpcT0G8ewpGNwLs2iP92fJfkuERolK7DCR/7WtlbuJ/a 3RA17qxiwfsP7d1pDT9v6nFfcahVzmtDPU9t0bFpWve0YhGOhS8cAf4KWeaS0PnCbHR3 Z+Fw==
MIME-Version: 1.0
Received: by 10.50.140.106 with SMTP id rf10mr13937472igb.41.1344974701299; Tue, 14 Aug 2012 13:05:01 -0700 (PDT)
Received: by 10.231.55.70 with HTTP; Tue, 14 Aug 2012 13:05:01 -0700 (PDT)
In-Reply-To: <502A821A.6080901@venaas.com>
References: <94C682931C08B048B7A8645303FDC9F36E4FC2D8C2@PUEXCB1B.nanterre.francetelecom.fr> <CAC8QAccH-72K7P3fj-uJB7x5L9xYsLF3W6xXATdtXrT6HB8Krw@mail.gmail.com> <502A821A.6080901@venaas.com>
Date: Tue, 14 Aug 2012 15:05:01 -0500
Message-ID: <CAC8QAcd2JP=H5_eXRhtoSoz6ytnV=oUqDWOot4j_THM3M5Ak_A@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Stig Venaas <stig@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 20:05:03 -0000

On Tue, Aug 14, 2012 at 11:51 AM, Stig Venaas <stig@venaas.com> wrote:
> On 8/14/2012 9:40 AM, Behcet Sarikaya wrote:
>>
>> On Tue, Aug 14, 2012 at 4:09 AM,  <mohamed.boucadair@orange.com> wrote:
>>>
>>> Dear all,
>>>
>>> I'm initiating this thread in the hope of understanding the
>>> objections from the 6man WG and hopefully to make some progress for
>>> this document.  To initiate the discussion, below are provided some
>>> preliminary Q/A:
>>>
>>> What is the scope of this document?
>>>     The document specifies an algorithmic translation of an IPv6
>>>     multicast address to a corresponding IPv4 multicast address, and
>>>     vice versa.  The document reserves two IPv6 multicast prefixes to
>>>     be used for that purpose.
>>>
>>> What are these reserved prefixes?
>>>     *  ff3x:0:8000::/96 for SSM
>>>     *  ffxx:8000::/20 for ASM
>>>
>>> Does this document update IPv6 addressing architecture?
>>>     No.
>>>
>>> Is there a unicast counterpart of this proposal?
>>>     Yes, RFC6052.
>>>
>>> What is the problem to be solved?
>>>     There are several use cases as detailed in [I-D.ietf-mboned-v4v6-
>>>     mcast-ps].  In particular, the following use cases are of
>>>     interest:
>>>     1.  An IPv6-only receiver wants to receive multicast content from
>>>         an IPv4-only source (6-4).
>>>     2.  An IPv4 receiver wants to join a multicast group in IPv4
>>>         domain via an IPv6-only network (4-6-4).
>>>
>>> Are there solutions for the unicast counterpart of these use cases?
>>>     Yes; various solutions including:
>>>     1.  6-4: RFC6146
>>>     2.  4-6-4: RFC6333, RFC6346, ...
>>
>>
>>
>> I don't understand why RFC 6333 is included here.
>> If you take a look at
>> http://tools.ietf.org/html/draft-sarikaya-softwire-dslitemulticast-01
>> there is no need for this draft.
>
>
> If I understand your draft correctly, it uses unicast for the
> encapsulation, then there is no need for this.
>
> But e.g. draft-ietf-softwire-dslite-multicast-02 needs it. If you are
> using multicast encapsulation (4 in 6), you need to know which group G
> or (S,G) to join at the tunnel egress point. And at the ingress, you
> need to interpret the IPv6 join you receive and extract the IPv4 address
> to know which IPv4 group is requested. For the latter part you could
> possibly encapsulate the joins, but I think that is not so good. Anyway,
> you need it for the first part.
>
> Encapsulation is very similar to translation. The only real difference
> I see, is that when you receive packets at the egress, you can just do
> decap, you don't need to figure out what the addresses in the new header
> should be.

First of all as Mboned chair said, multicast can be tunneled, i.e.
encapsulated. AMT is an example. DS-Lite tunnel as in
draft-sarikaya-softwire-dslitemulticast-01 is another example.

The point here is that draft-ietf-mboned-64-multicast-address-format
describes part of translation multicast and it should be explained as
such. Encapsulation or tunneling has nothing to do with it.

Hope this clarifies my point and we don't keep coming back to this again.

Regards,

Behcet

From stig@venaas.com  Tue Aug 14 13:46:59 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D23421E808E for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 13:46:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.445
X-Spam-Level: 
X-Spam-Status: No, score=-102.445 tagged_above=-999 required=5 tests=[AWL=0.155, 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 LpBIR6qRbaKk for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 13:46:58 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id C8AB921E8085 for <mboned@ietf.org>; Tue, 14 Aug 2012 13:46:54 -0700 (PDT)
Received: from [IPv6:2001:420:301:1004:68c6:e400:af0d:86da] (unknown [IPv6:2001:420:301:1004:68c6:e400:af0d:86da]) by ufisa.uninett.no (Postfix) with ESMTPSA id 0D8017FE3; Tue, 14 Aug 2012 22:46:52 +0200 (CEST)
Message-ID: <502AB938.10301@venaas.com>
Date: Tue, 14 Aug 2012 13:46:48 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: sarikaya@ieee.org
References: <94C682931C08B048B7A8645303FDC9F36E4FC2D8C2@PUEXCB1B.nanterre.francetelecom.fr> <CAC8QAccH-72K7P3fj-uJB7x5L9xYsLF3W6xXATdtXrT6HB8Krw@mail.gmail.com> <502A821A.6080901@venaas.com> <CAC8QAcd2JP=H5_eXRhtoSoz6ytnV=oUqDWOot4j_THM3M5Ak_A@mail.gmail.com>
In-Reply-To: <CAC8QAcd2JP=H5_eXRhtoSoz6ytnV=oUqDWOot4j_THM3M5Ak_A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: MBONED WG <mboned@ietf.org>, Behcet Sarikaya <sarikaya2012@gmail.com>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 20:46:59 -0000

On 8/14/2012 1:05 PM, Behcet Sarikaya wrote:
> On Tue, Aug 14, 2012 at 11:51 AM, Stig Venaas <stig@venaas.com> wrote:
>> On 8/14/2012 9:40 AM, Behcet Sarikaya wrote:
>>>
>>> On Tue, Aug 14, 2012 at 4:09 AM,  <mohamed.boucadair@orange.com> wrote:
>>>>
>>>> Dear all,
>>>>
>>>> I'm initiating this thread in the hope of understanding the
>>>> objections from the 6man WG and hopefully to make some progress for
>>>> this document.  To initiate the discussion, below are provided some
>>>> preliminary Q/A:
>>>>
>>>> What is the scope of this document?
>>>>      The document specifies an algorithmic translation of an IPv6
>>>>      multicast address to a corresponding IPv4 multicast address, and
>>>>      vice versa.  The document reserves two IPv6 multicast prefixes to
>>>>      be used for that purpose.
>>>>
>>>> What are these reserved prefixes?
>>>>      *  ff3x:0:8000::/96 for SSM
>>>>      *  ffxx:8000::/20 for ASM
>>>>
>>>> Does this document update IPv6 addressing architecture?
>>>>      No.
>>>>
>>>> Is there a unicast counterpart of this proposal?
>>>>      Yes, RFC6052.
>>>>
>>>> What is the problem to be solved?
>>>>      There are several use cases as detailed in [I-D.ietf-mboned-v4v6-
>>>>      mcast-ps].  In particular, the following use cases are of
>>>>      interest:
>>>>      1.  An IPv6-only receiver wants to receive multicast content from
>>>>          an IPv4-only source (6-4).
>>>>      2.  An IPv4 receiver wants to join a multicast group in IPv4
>>>>          domain via an IPv6-only network (4-6-4).
>>>>
>>>> Are there solutions for the unicast counterpart of these use cases?
>>>>      Yes; various solutions including:
>>>>      1.  6-4: RFC6146
>>>>      2.  4-6-4: RFC6333, RFC6346, ...
>>>
>>>
>>>
>>> I don't understand why RFC 6333 is included here.
>>> If you take a look at
>>> http://tools.ietf.org/html/draft-sarikaya-softwire-dslitemulticast-01
>>> there is no need for this draft.
>>
>>
>> If I understand your draft correctly, it uses unicast for the
>> encapsulation, then there is no need for this.
>>
>> But e.g. draft-ietf-softwire-dslite-multicast-02 needs it. If you are
>> using multicast encapsulation (4 in 6), you need to know which group G
>> or (S,G) to join at the tunnel egress point. And at the ingress, you
>> need to interpret the IPv6 join you receive and extract the IPv4 address
>> to know which IPv4 group is requested. For the latter part you could
>> possibly encapsulate the joins, but I think that is not so good. Anyway,
>> you need it for the first part.
>>
>> Encapsulation is very similar to translation. The only real difference
>> I see, is that when you receive packets at the egress, you can just do
>> decap, you don't need to figure out what the addresses in the new header
>> should be.
>
> First of all as Mboned chair said, multicast can be tunneled, i.e.
> encapsulated. AMT is an example. DS-Lite tunnel as in
> draft-sarikaya-softwire-dslitemulticast-01 is another example.

Yes, and I'm trying to explain why this solution applies to
tunneling. draft-ietf-softwire-dslite-multicast-02 is one example.

> The point here is that draft-ietf-mboned-64-multicast-address-format
> describes part of translation multicast and it should be explained as
> such. Encapsulation or tunneling has nothing to do with it.

And I was trying to explain above why it is also part of encapsulation.

Stig

> Hope this clarifies my point and we don't keep coming back to this again.
>
> Regards,
>
> Behcet
>


From yiu_lee@cable.comcast.com  Tue Aug 14 14:43:42 2012
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0724221E80BA for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 14:43:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.108
X-Spam-Level: 
X-Spam-Status: No, score=-104.108 tagged_above=-999 required=5 tests=[AWL=1.123, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_MED=-4, 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 DK1g1lnQ7jT9 for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 14:43:41 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id D30C721E80B9 for <mboned@ietf.org>; Tue, 14 Aug 2012 14:43:40 -0700 (PDT)
Received: from ([24.40.56.116]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.29320025; Tue, 14 Aug 2012 15:23:45 -0600
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.115]) by pacdcexhub03.cable.comcast.com ([fe80::5527:6d6b:29a7:f414%13]) with mapi id 14.02.0309.002; Tue, 14 Aug 2012 17:43:36 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Stig Venaas <stig@venaas.com>, Brian Haberman <brian@innovationslab.net>
Thread-Topic: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
Thread-Index: AQHNemXbrMKrO7WKH0yhbbHzP3P4hg==
Date: Tue, 14 Aug 2012 21:43:36 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <50298B3E.2020207@venaas.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [24.40.55.72]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3427811014_2138494"
MIME-Version: 1.0
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 21:43:42 -0000

--B_3427811014_2138494
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hi Stig,

Since we want T=1, this will not meet the "well-known" requirement defined
in RFC4291. If we don't want to define a flag, what is the proper way to
describe ffxx:8000::/20 and ffxx:0:8000::/96?

Thanks,
Yiu


On 8/13/12 7:18 PM, "Stig Venaas" <stig@venaas.com> wrote:

>On 13.08.2012 14:46, Brian Haberman wrote:
>> On 8/13/12 4:21 PM, Behcet Sarikaya wrote:
>>> Hi authors,
>>>
>>> Thanks for the revised draft, I find that the revision is in the right
>>> direction.
>>>
>>> I am confused on the prefix lengths:
>>> on Figure 2,
>>> ffxx:8000:0:abc::/96
>>> while in Section 3.1
>>> ffxx:8000::/20
>>>
>>
>> The x's correspond to the flags and scope fields within the multicast
>> address.  Take a look at:
>>
>> 
>>http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-a
>>ddresses.xml#ipv6-multicast-addresses-4
>
>We have one minor issue here though. They cannot simply be IANA
>allocations, since they would not have the transient bit set. In
>this case, the idea is that it should work for flag nibble values
>like 1, 3 and 7. Actually I believe the transient bit should always
>be set for these groups.
>
>Stig
>
>>
>>
>>> How come these are reserved prefixes?
>>> What are the values that are reserved?
>>>
>>> If you look at RFC 6052, the unicast translation specification,
>>> 64:ff9b::/96 is defined as the Well-Known Prefix. There are no x's in
>>> the prefix definition.
>>>
>>> Regards,
>>>
>>> Behcet
>>>
>>> On Fri, Aug 10, 2012 at 1:49 AM,  <internet-drafts@ietf.org> wrote:
>>>>
>>>> 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           : IPv6 Multicast Address With Embedded IPv4
>>>> Multicast Address
>>>>          Author(s)       : Mohamed Boucadair
>>>>                            Jacni Qin
>>>>                            Yiu L. Lee
>>>>                            Stig Venaas
>>>>                            Xing Li
>>>>                            Mingwei Xu
>>>>          Filename        :
>>>> draft-ietf-mboned-64-multicast-address-format-03.txt
>>>>          Pages           : 13
>>>>          Date            : 2012-08-09
>>>>
>>>> Abstract:
>>>>     This document reserves two IPv6 multicast prefixes to be used in
>>>>the
>>>>     context of IPv4-IPv6 interconnection.  The document specifies an
>>>>     algorithmic translation of an IPv6 multicast address to a
>>>>     corresponding IPv4 multicast address, and vice versa.  This
>>>>     algorithmic translation can be used in both IPv4-IPv6 translation
>>>>or
>>>>     encapsulation schemes.
>>>>
>>>>
>>>>
>>>> The IETF datatracker status page for this draft is:
>>>> 
>>>>https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast-address
>>>>-format
>>>>
>>>>
>>>> There's also a htmlized version available at:
>>>> 
>>>>http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-forma
>>>>t-03
>>>>
>>>>
>>>> A diff from the previous version is available at:
>>>> 
>>>>http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-64-multicast-address
>>>>-format-03
>>>>
>>>>
>>>>
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>
>>>> _______________________________________________
>>>> MBONED mailing list
>>>> MBONED@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mboned
>>> _______________________________________________
>>> MBONED mailing list
>>> MBONED@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mboned
>>>
>>
>>
>> _______________________________________________
>> MBONED mailing list
>> MBONED@ietf.org
>> https://www.ietf.org/mailman/listinfo/mboned
>
>_______________________________________________
>MBONED mailing list
>MBONED@ietf.org
>https://www.ietf.org/mailman/listinfo/mboned

--B_3427811014_2138494
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIVlwYJKoZIhvcNAQcCoIIViDCCFYQCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EzAwggUzMIIEG6ADAgECAhBTm5vcGTrcIPdnvVTe3rDkMA0GCSqGSIb3DQEBBQUAMIGTMQsw
CQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxm
b3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVu
dCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTEyMDIxNDAwMDAwMFoX
DTEzMDIxMzIzNTk1OVowKjEoMCYGCSqGSIb3DQEJARYZeWl1X2xlZUBjYWJsZS5jb21jYXN0
LmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANOm2q1Oat5U5a79IA1Yx+oa
djvccI4HQYLkQtDXj9an1bz7JT52yBADiZJ42pTJ35L4yPzYRY/4b1k7RCsodmRzu4F2n1wA
Xjg3hkRygwiAVrEv7p1FM4Wsr4nY6utC6/dhrJFkTtLzMmQXcSeVF1gpoaDKzf9UNvXNZCy8
dpLhdP4v8t7JOhfPyR3LBOo7vKk4WIv7ugGVgyLXwGSwu0rEVNOwLtPdoTJW0pi+ATaJeAuf
WVIKLRVjK56vKBeA3ms3BJNOp5zkfAk5j3IymZZMD156Tib5ViL8dCTycYZyMNWBOrDPC/yn
c4itE6q05Wh94QYGp6GcsZkiHEXFZrUCAwEAAaOCAekwggHlMB8GA1UdIwQYMBaAFHoTTgB0
W8Z4Y2QnwS/ioFu8ecV7MB0GA1UdDgQWBBTdz82GEvcyRLU/wx9KzuYvjgUddzAOBgNVHQ8B
Af8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQED
BQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYI
KwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMFcGA1UdHwRQME4wTKBK
oEiGRmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9u
YW5kU2VjdXJlRW1haWxDQS5jcmwwgYgGCCsGAQUFBwEBBHwwejBSBggrBgEFBQcwAoZGaHR0
cDovL2NydC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1
cmVFbWFpbENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuY29tb2RvY2EuY29tMCQG
A1UdEQQdMBuBGXlpdV9sZWVAY2FibGUuY29tY2FzdC5jb20wDQYJKoZIhvcNAQEFBQADggEB
AFeEfwmWgj/jpA3+ctSoBsbvHGnWLz00p8NBX2+qzz8QjgDpZT5T1Fux5MV6qlVJpND12pzq
ziUyFCBdv6QOMyiOrn5RxooXY9W6Hpa8qBD4v9BXy5qtP7gi4xJhFufXdNZXEw2RwNyjBzfV
/F2Q8HSwlyOwS+fHKYZZ9gy/KneVP//YcrC4icG1ipJQ2+gCUs+uUAouz0xF0uBYE/bQRTss
oRTY6D/X5lxarw28oocfr38v4Ro5bmsZlsEF22OvpKZX5tfz1aOL5U9nhXixY7Sd9B9BGHl7
mrybVUl7NnguWGIAhHiVD9ce1u4jJ1PnNmrNkvwJouS/7zYCId8000cwggUaMIIEAqADAgEC
AhBtGeqnGU9qMyLmIjJ6qnHeMA0GCSqGSIb3DQEBBQUAMIGuMQswCQYDVQQGEwJVUzELMAkG
A1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRS
VVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UE
AxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMB4XDTEx
MDQyODAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJH
cmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD
QSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBT
ZWN1cmUgRW1haWwgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCShIRbS1eY
1F4vi6ThQMijU1hfZmXxMk73nzJ9VdB4TFW3QpTg+SdxB8XGaaS5MsTxQBqQzCdWYn8XtXFp
ruUgG+TLY15gyqJB9mrho/+43x9IbWVDjCouK2M4d9+xF6zC2oIC1tQyatRnbyATj1w1+uVU
gK/YcQodNwoCUFNslR2pEBS0mZVZEjH/CaLSTNxS297iQAFbSGjdxUq04O0kHzqvcV8H46y/
FDuwJXFoPfQP1hdYRhWBPGiLi4MPbXohV+Y0sNsyfuNK4aVScmQmkU6lkg//4LFg/RpvaFGZ
Y40ai6XMQpubfSJj06mg/M6ekN9EGfRcWzW6FvOnm//BAgMBAAGjggFLMIIBRzAfBgNVHSME
GDAWgBSJgmd9xJ0mcABLtFBIfN49rgRufTAdBgNVHQ4EFgQUehNOAHRbxnhjZCfBL+KgW7x5
xXswDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8CAQAwEQYDVR0gBAowCDAGBgRV
HSAAMFgGA1UdHwRRME8wTaBLoEmGR2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9VVE4tVVNF
UkZpcnN0LUNsaWVudEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMHQGCCsGAQUFBwEBBGgw
ZjA9BggrBgEFBQcwAoYxaHR0cDovL2NydC51c2VydHJ1c3QuY29tL1VUTkFkZFRydXN0Q2xp
ZW50X0NBLmNydDAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTANBgkq
hkiG9w0BAQUFAAOCAQEAhda+eFdVbTN/RFL+QtUGqAEDgIr7DbL9Sr/2r0FJ9RtaxdKtG3Nu
PukmfOZMmMEwKN/L+0I8oSU+CnXW0D05hmbRoZu1TZtvryhsHa/l6nRaqNqxwPF1ei+eupN5
yv7ikR5WdLL4jdPgQ3Ib7Y/9YDkgR/uLrzplSDyYPaUlv73vYOBJ5RbI6z9Dg/Dg7g3B080z
X5vQvWBqszv++tTJOjwf7Zv/m0kzvkIpOYPuM2kugp1FTahp2oAbHj3SGl18R5mlmwhtEpmG
1l1XBxunML5LSUS4kH7K0Xk467Qz+qA6XSZYnmFVGLQh1ZnV4ENAQjC+6qXnlNKw/vN1+X9u
5zCCBJ0wggOFoAMCAQICEDQ96SusJzT/j8s0lPvMcFQwDQYJKoZIhvcNAQEFBQAwbzELMAkG
A1UEBhMCU0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRl
cm5hbCBUVFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAe
Fw0wNTA2MDcwODA5MTBaFw0yMDA1MzAxMDQ4MzhaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UE
CBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNU
IE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMt
VVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxq
mNVNNRm5pELlzkniii8efNIxB8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPM
yaQylbsMTzC9mKALi+VuG6JG+ni8om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbN
oKXqvgvOdjp6Dpvq/NonWz1zHyLmSGHGTPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcR
Wdq6hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7NlyP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/
MLbu9mIwFIws6wIDAQABo4H0MIHxMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1Qa
MB0GA1UdDgQWBBSJgmd9xJ0mcABLtFBIfN49rgRufTAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0T
AQH/BAUwAwEB/zARBgNVHSAECjAIMAYGBFUdIAAwRAYDVR0fBD0wOzA5oDegNYYzaHR0cDov
L2NybC51c2VydHJ1c3QuY29tL0FkZFRydXN0RXh0ZXJuYWxDQVJvb3QuY3JsMDUGCCsGAQUF
BwEBBCkwJzAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTANBgkqhkiG
9w0BAQUFAAOCAQEAAbyc42MosPMxAcLfe91ioAGdIzEPnJJzU1HqH0z61p/Eyi9nfngzD3QW
uZGHkfWKJvpkcADYHvkLBGJQh5OB1Nr1I9s0u4VWtHA0bniDNx6FHMURFZJfhxe9rGr98cLR
zIlfsXzwPlHyNfN87GCYazor4O/fs32G67Ub9VvsonyYE9cAULnRLXPeA3h04QWFMV7Lmrmd
lMa5lDd1ctxE+2fo8PolHlKn2iXpR+CgxzygTrEKNvt3SJ/vl4r7tP7jlBSog7xcLT/SYHFg
7sJxggzpiDbj2iC0o6BsqpZLuICOdcpJB/Y7FLrf3AXZn9vgsuZNoHgm5+ctbn9fxh6IFTCC
BDYwggMeoAMCAQICAQEwDQYJKoZIhvcNAQEFBQAwbzELMAkGA1UEBhMCU0UxFDASBgNVBAoT
C0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBUVFAgTmV0d29yazEi
MCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAeFw0wMDA1MzAxMDQ4MzhaFw0y
MDA1MzAxMDQ4MzhaMG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQG
A1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0
IEV4dGVybmFsIENBIFJvb3QwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC39xoz
5vIABC054E5b7R+8bA/Ntfojts7emxEzl6QpTH2Tn71KvJPtAxrjj8/lbVBa1pcplFqAsEl6
2y6V/bjKvzc4LR4+kUGtcFbH8E8/6DKedMrIkFTpxl8PeJ2aQDwOrGGqXhSPnoehalDc15pO
rwWzpnGUnHGzUGAKxxOdOAeGAqjpqGkmGJCrTLBPI6s6T4TY386f4Wlvu9dC12tE5Met7m1B
X3JacQg3s3llpFmglDf3AC8NwpJy2tA4ctsUqEXEXSp9t7TWxO6szRNEt8kr3UMAJfphuWlq
WCMRt6czj1Z1WfXNKddGtworZbbTQm8Vsrh7++/pXVPVNFonAgMBAAGjgdwwgdkwHQYDVR0O
BBYEFK29mHo0tCb3+sQmVO8DveAky1QaMAsGA1UdDwQEAwIBBjAPBgNVHRMBAf8EBTADAQH/
MIGZBgNVHSMEgZEwgY6AFK29mHo0tCb3+sQmVO8DveAky1QaoXOkcTBvMQswCQYDVQQGEwJT
RTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRU
UCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290ggEBMA0GCSqG
SIb3DQEBBQUAA4IBAQCwm+CFJcLWI+IPlgaSnUGYnNmEeYHZHlsUByM2ZY+w2He7rEFsR2CD
UbD5Mj3n/PYmE8eAFqW/WvyHz3h5iSGa4kwHCoY1vPLeUcTSlrfcfk7ucP0cOesMAlEULY69
FuDB30Z15ySt7PRCtIWTcBBnup0GNUoY0yt6zFFCoXpj0ea7ocUrwja+Ew3mvWN+eXunCQ1A
q2rdj4rD9vaMGkIFUdRF9Z+nYiFoFSBDPJnnfL0k2KmRF3OIP1YbMTgYtHEPms3IDp6OLhvh
jJiDyx8x8URMxgRzSXZgD8f4vReAay7pzEwOWpp5DyAKLtWeYyYeVZKU2IIXWnvQvMePToYE
MYICLzCCAisCAQEwgagwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNo
ZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkw
NwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwg
Q0ECEFObm9wZOtwg92e9VN7esOQwCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJBDEWBBTHDiAr
Tha3NFNZ90zH55mlW13aWDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ
BTEPFw0xMjA4MTQyMTQzMzRaMA0GCSqGSIb3DQEBAQUABIIBAAApxIei9T4ZmBDT7QfOBylf
DxONrHDx1Db15IWNttxUubgwQsL1GUFcdch++4ycOuntRcGO2yW3CpOrYzOlPHOPicdm19ds
s44/df1l8LIjU8CO3oa8JwBrblkU++vcayOyUaKLmKz7MN1PN2L6tbbP19kKGCr3MAsE6v/1
3+xQMKVIVWxWt3KmTUtB6LI/kU0KzZ8XUzavrQeJucfU0KGdXT9drOJ51YQr4TDxkNVYUzrm
m1V7FkgRWrDD9pmqnm3nc7jpOi3KZXeYW8BxTW8/3JR8AJ8rVOMDCfFOzL1XOBN7fNWpsNh4
xTscWipBvAZXCmBO1gnXRBDrruhfDeQ=

--B_3427811014_2138494--

From yiu_lee@cable.comcast.com  Tue Aug 14 14:44:35 2012
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3178821E80B7 for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 14:44:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.152
X-Spam-Level: 
X-Spam-Status: No, score=-104.152 tagged_above=-999 required=5 tests=[AWL=1.079, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_MED=-4, 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 dVI75-y5fdth for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 14:44:34 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 6F09921E80B4 for <mboned@ietf.org>; Tue, 14 Aug 2012 14:44:34 -0700 (PDT)
Received: from ([24.40.56.116]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.29320114; Tue, 14 Aug 2012 15:24:23 -0600
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.115]) by pacdcexhub03.cable.comcast.com ([fe80::5527:6d6b:29a7:f414%13]) with mapi id 14.02.0309.002; Tue, 14 Aug 2012 17:44:14 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>, Stig Venaas <stig@venaas.com>
Thread-Topic: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
Thread-Index: AQHNemXxrMKrO7WKH0yhbbHzP3P4hg==
Date: Tue, 14 Aug 2012 21:44:13 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD379D3774@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <CAC8QAcc4V3x=AG+XC-bOupkKzyfOTJDR2b=RBiJBgojd7A9LaA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [24.40.55.72]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3427811053_2167476"
MIME-Version: 1.0
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 21:44:35 -0000

--B_3427811053_2167476
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hi Behcet,

Note taken. Thanks!


On 8/14/12 12:54 PM, "Behcet Sarikaya" <sarikaya2012@gmail.com> wrote:

>On Mon, Aug 13, 2012 at 6:18 PM, Stig Venaas <stig@venaas.com> wrote:
>> On 13.08.2012 14:46, Brian Haberman wrote:
>>>
>>> On 8/13/12 4:21 PM, Behcet Sarikaya wrote:
>>>>
>>>> Hi authors,
>>>>
>>>> Thanks for the revised draft, I find that the revision is in the right
>>>> direction.
>>>>
>>>> I am confused on the prefix lengths:
>>>> on Figure 2,
>>>> ffxx:8000:0:abc::/96
>>>> while in Section 3.1
>>>> ffxx:8000::/20
>>>>
>>>
>>> The x's correspond to the flags and scope fields within the multicast
>>> address.  Take a look at:
>>>
>>>
>>> 
>>>http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-
>>>addresses.xml#ipv6-multicast-addresses-4
>>
>>
>> We have one minor issue here though. They cannot simply be IANA
>> allocations, since they would not have the transient bit set. In
>> this case, the idea is that it should work for flag nibble values
>> like 1, 3 and 7. Actually I believe the transient bit should always
>> be set for these groups.
>
>I think it will be better to clarify in the draft saying that xx
>corresponds to flgs and scop fields defined in RFC 3306.
>
>Regards,
>
>Behcet
>
>>
>> Stig
>>
>>
>>>
>>>
>>>> How come these are reserved prefixes?
>>>> What are the values that are reserved?
>>>>
>>>> If you look at RFC 6052, the unicast translation specification,
>>>> 64:ff9b::/96 is defined as the Well-Known Prefix. There are no x's in
>>>> the prefix definition.
>>>>
>>>> Regards,
>>>>
>>>> Behcet
>>>>
>>>> On Fri, Aug 10, 2012 at 1:49 AM,  <internet-drafts@ietf.org> wrote:
>>>>>
>>>>>
>>>>> 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           : IPv6 Multicast Address With Embedded IPv4
>>>>> Multicast Address
>>>>>          Author(s)       : Mohamed Boucadair
>>>>>                            Jacni Qin
>>>>>                            Yiu L. Lee
>>>>>                            Stig Venaas
>>>>>                            Xing Li
>>>>>                            Mingwei Xu
>>>>>          Filename        :
>>>>> draft-ietf-mboned-64-multicast-address-format-03.txt
>>>>>          Pages           : 13
>>>>>          Date            : 2012-08-09
>>>>>
>>>>> Abstract:
>>>>>     This document reserves two IPv6 multicast prefixes to be used in
>>>>>the
>>>>>     context of IPv4-IPv6 interconnection.  The document specifies an
>>>>>     algorithmic translation of an IPv6 multicast address to a
>>>>>     corresponding IPv4 multicast address, and vice versa.  This
>>>>>     algorithmic translation can be used in both IPv4-IPv6
>>>>>translation or
>>>>>     encapsulation schemes.
>>>>>
>>>>>
>>>>>
>>>>> The IETF datatracker status page for this draft is:
>>>>>
>>>>> 
>>>>>https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast-addres
>>>>>s-format
>>>>>
>>>>>
>>>>> There's also a htmlized version available at:
>>>>>
>>>>> 
>>>>>http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-form
>>>>>at-03
>>>>>
>>>>>
>>>>> A diff from the previous version is available at:
>>>>>
>>>>> 
>>>>>http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-64-multicast-addres
>>>>>s-format-03
>>>>>
>>>>>
>>>>>
>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>
>>>>> _______________________________________________
>>>>> MBONED mailing list
>>>>> MBONED@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>>
>>>> _______________________________________________
>>>> MBONED mailing list
>>>> MBONED@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>>
>>>
>>>
>>> _______________________________________________
>>> MBONED mailing list
>>> MBONED@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mboned
>>
>>
>> _______________________________________________
>> MBONED mailing list
>> MBONED@ietf.org
>> https://www.ietf.org/mailman/listinfo/mboned
>_______________________________________________
>MBONED mailing list
>MBONED@ietf.org
>https://www.ietf.org/mailman/listinfo/mboned

--B_3427811053_2167476
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIVlwYJKoZIhvcNAQcCoIIViDCCFYQCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EzAwggUzMIIEG6ADAgECAhBTm5vcGTrcIPdnvVTe3rDkMA0GCSqGSIb3DQEBBQUAMIGTMQsw
CQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxm
b3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVu
dCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTEyMDIxNDAwMDAwMFoX
DTEzMDIxMzIzNTk1OVowKjEoMCYGCSqGSIb3DQEJARYZeWl1X2xlZUBjYWJsZS5jb21jYXN0
LmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANOm2q1Oat5U5a79IA1Yx+oa
djvccI4HQYLkQtDXj9an1bz7JT52yBADiZJ42pTJ35L4yPzYRY/4b1k7RCsodmRzu4F2n1wA
Xjg3hkRygwiAVrEv7p1FM4Wsr4nY6utC6/dhrJFkTtLzMmQXcSeVF1gpoaDKzf9UNvXNZCy8
dpLhdP4v8t7JOhfPyR3LBOo7vKk4WIv7ugGVgyLXwGSwu0rEVNOwLtPdoTJW0pi+ATaJeAuf
WVIKLRVjK56vKBeA3ms3BJNOp5zkfAk5j3IymZZMD156Tib5ViL8dCTycYZyMNWBOrDPC/yn
c4itE6q05Wh94QYGp6GcsZkiHEXFZrUCAwEAAaOCAekwggHlMB8GA1UdIwQYMBaAFHoTTgB0
W8Z4Y2QnwS/ioFu8ecV7MB0GA1UdDgQWBBTdz82GEvcyRLU/wx9KzuYvjgUddzAOBgNVHQ8B
Af8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQED
BQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYI
KwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMFcGA1UdHwRQME4wTKBK
oEiGRmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9u
YW5kU2VjdXJlRW1haWxDQS5jcmwwgYgGCCsGAQUFBwEBBHwwejBSBggrBgEFBQcwAoZGaHR0
cDovL2NydC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1
cmVFbWFpbENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuY29tb2RvY2EuY29tMCQG
A1UdEQQdMBuBGXlpdV9sZWVAY2FibGUuY29tY2FzdC5jb20wDQYJKoZIhvcNAQEFBQADggEB
AFeEfwmWgj/jpA3+ctSoBsbvHGnWLz00p8NBX2+qzz8QjgDpZT5T1Fux5MV6qlVJpND12pzq
ziUyFCBdv6QOMyiOrn5RxooXY9W6Hpa8qBD4v9BXy5qtP7gi4xJhFufXdNZXEw2RwNyjBzfV
/F2Q8HSwlyOwS+fHKYZZ9gy/KneVP//YcrC4icG1ipJQ2+gCUs+uUAouz0xF0uBYE/bQRTss
oRTY6D/X5lxarw28oocfr38v4Ro5bmsZlsEF22OvpKZX5tfz1aOL5U9nhXixY7Sd9B9BGHl7
mrybVUl7NnguWGIAhHiVD9ce1u4jJ1PnNmrNkvwJouS/7zYCId8000cwggUaMIIEAqADAgEC
AhBtGeqnGU9qMyLmIjJ6qnHeMA0GCSqGSIb3DQEBBQUAMIGuMQswCQYDVQQGEwJVUzELMAkG
A1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRS
VVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UE
AxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMB4XDTEx
MDQyODAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJH
cmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD
QSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBT
ZWN1cmUgRW1haWwgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCShIRbS1eY
1F4vi6ThQMijU1hfZmXxMk73nzJ9VdB4TFW3QpTg+SdxB8XGaaS5MsTxQBqQzCdWYn8XtXFp
ruUgG+TLY15gyqJB9mrho/+43x9IbWVDjCouK2M4d9+xF6zC2oIC1tQyatRnbyATj1w1+uVU
gK/YcQodNwoCUFNslR2pEBS0mZVZEjH/CaLSTNxS297iQAFbSGjdxUq04O0kHzqvcV8H46y/
FDuwJXFoPfQP1hdYRhWBPGiLi4MPbXohV+Y0sNsyfuNK4aVScmQmkU6lkg//4LFg/RpvaFGZ
Y40ai6XMQpubfSJj06mg/M6ekN9EGfRcWzW6FvOnm//BAgMBAAGjggFLMIIBRzAfBgNVHSME
GDAWgBSJgmd9xJ0mcABLtFBIfN49rgRufTAdBgNVHQ4EFgQUehNOAHRbxnhjZCfBL+KgW7x5
xXswDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8CAQAwEQYDVR0gBAowCDAGBgRV
HSAAMFgGA1UdHwRRME8wTaBLoEmGR2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9VVE4tVVNF
UkZpcnN0LUNsaWVudEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMHQGCCsGAQUFBwEBBGgw
ZjA9BggrBgEFBQcwAoYxaHR0cDovL2NydC51c2VydHJ1c3QuY29tL1VUTkFkZFRydXN0Q2xp
ZW50X0NBLmNydDAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTANBgkq
hkiG9w0BAQUFAAOCAQEAhda+eFdVbTN/RFL+QtUGqAEDgIr7DbL9Sr/2r0FJ9RtaxdKtG3Nu
PukmfOZMmMEwKN/L+0I8oSU+CnXW0D05hmbRoZu1TZtvryhsHa/l6nRaqNqxwPF1ei+eupN5
yv7ikR5WdLL4jdPgQ3Ib7Y/9YDkgR/uLrzplSDyYPaUlv73vYOBJ5RbI6z9Dg/Dg7g3B080z
X5vQvWBqszv++tTJOjwf7Zv/m0kzvkIpOYPuM2kugp1FTahp2oAbHj3SGl18R5mlmwhtEpmG
1l1XBxunML5LSUS4kH7K0Xk467Qz+qA6XSZYnmFVGLQh1ZnV4ENAQjC+6qXnlNKw/vN1+X9u
5zCCBJ0wggOFoAMCAQICEDQ96SusJzT/j8s0lPvMcFQwDQYJKoZIhvcNAQEFBQAwbzELMAkG
A1UEBhMCU0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRl
cm5hbCBUVFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAe
Fw0wNTA2MDcwODA5MTBaFw0yMDA1MzAxMDQ4MzhaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UE
CBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNU
IE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMt
VVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxq
mNVNNRm5pELlzkniii8efNIxB8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPM
yaQylbsMTzC9mKALi+VuG6JG+ni8om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbN
oKXqvgvOdjp6Dpvq/NonWz1zHyLmSGHGTPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcR
Wdq6hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7NlyP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/
MLbu9mIwFIws6wIDAQABo4H0MIHxMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1Qa
MB0GA1UdDgQWBBSJgmd9xJ0mcABLtFBIfN49rgRufTAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0T
AQH/BAUwAwEB/zARBgNVHSAECjAIMAYGBFUdIAAwRAYDVR0fBD0wOzA5oDegNYYzaHR0cDov
L2NybC51c2VydHJ1c3QuY29tL0FkZFRydXN0RXh0ZXJuYWxDQVJvb3QuY3JsMDUGCCsGAQUF
BwEBBCkwJzAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTANBgkqhkiG
9w0BAQUFAAOCAQEAAbyc42MosPMxAcLfe91ioAGdIzEPnJJzU1HqH0z61p/Eyi9nfngzD3QW
uZGHkfWKJvpkcADYHvkLBGJQh5OB1Nr1I9s0u4VWtHA0bniDNx6FHMURFZJfhxe9rGr98cLR
zIlfsXzwPlHyNfN87GCYazor4O/fs32G67Ub9VvsonyYE9cAULnRLXPeA3h04QWFMV7Lmrmd
lMa5lDd1ctxE+2fo8PolHlKn2iXpR+CgxzygTrEKNvt3SJ/vl4r7tP7jlBSog7xcLT/SYHFg
7sJxggzpiDbj2iC0o6BsqpZLuICOdcpJB/Y7FLrf3AXZn9vgsuZNoHgm5+ctbn9fxh6IFTCC
BDYwggMeoAMCAQICAQEwDQYJKoZIhvcNAQEFBQAwbzELMAkGA1UEBhMCU0UxFDASBgNVBAoT
C0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBUVFAgTmV0d29yazEi
MCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAeFw0wMDA1MzAxMDQ4MzhaFw0y
MDA1MzAxMDQ4MzhaMG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQG
A1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0
IEV4dGVybmFsIENBIFJvb3QwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC39xoz
5vIABC054E5b7R+8bA/Ntfojts7emxEzl6QpTH2Tn71KvJPtAxrjj8/lbVBa1pcplFqAsEl6
2y6V/bjKvzc4LR4+kUGtcFbH8E8/6DKedMrIkFTpxl8PeJ2aQDwOrGGqXhSPnoehalDc15pO
rwWzpnGUnHGzUGAKxxOdOAeGAqjpqGkmGJCrTLBPI6s6T4TY386f4Wlvu9dC12tE5Met7m1B
X3JacQg3s3llpFmglDf3AC8NwpJy2tA4ctsUqEXEXSp9t7TWxO6szRNEt8kr3UMAJfphuWlq
WCMRt6czj1Z1WfXNKddGtworZbbTQm8Vsrh7++/pXVPVNFonAgMBAAGjgdwwgdkwHQYDVR0O
BBYEFK29mHo0tCb3+sQmVO8DveAky1QaMAsGA1UdDwQEAwIBBjAPBgNVHRMBAf8EBTADAQH/
MIGZBgNVHSMEgZEwgY6AFK29mHo0tCb3+sQmVO8DveAky1QaoXOkcTBvMQswCQYDVQQGEwJT
RTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRU
UCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290ggEBMA0GCSqG
SIb3DQEBBQUAA4IBAQCwm+CFJcLWI+IPlgaSnUGYnNmEeYHZHlsUByM2ZY+w2He7rEFsR2CD
UbD5Mj3n/PYmE8eAFqW/WvyHz3h5iSGa4kwHCoY1vPLeUcTSlrfcfk7ucP0cOesMAlEULY69
FuDB30Z15ySt7PRCtIWTcBBnup0GNUoY0yt6zFFCoXpj0ea7ocUrwja+Ew3mvWN+eXunCQ1A
q2rdj4rD9vaMGkIFUdRF9Z+nYiFoFSBDPJnnfL0k2KmRF3OIP1YbMTgYtHEPms3IDp6OLhvh
jJiDyx8x8URMxgRzSXZgD8f4vReAay7pzEwOWpp5DyAKLtWeYyYeVZKU2IIXWnvQvMePToYE
MYICLzCCAisCAQEwgagwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNo
ZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkw
NwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwg
Q0ECEFObm9wZOtwg92e9VN7esOQwCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJBDEWBBTSkFU7
qu7mLA7Fbb08xJ8OzaWxATAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ
BTEPFw0xMjA4MTQyMTQ0MTFaMA0GCSqGSIb3DQEBAQUABIIBAC93cdR4wCcOxN3YixZrd2oA
oCHlv8yXq4CwMAh0uTA3/vZOqu6dRJzH1OX7tHXRZS0laOi9p2coH6SILCcJn2lEW3tSxNZ1
cUBFhkIwSN3uXtf5upt31kCfH7CW1qkT+t+dxyNL2qLC8iHB4lXcNcoGeBgxKWSAkc0HOFXd
xNxyomCu/gkXAuoLv6qnG/+nMzcrL8w+tJNaMYZRIsajLBs6YuAway+C7K7wNDq+mr4DZft6
/HQQQMAP1w4EtO56dHq7h2sHKirlFepvfCbu+2uU0MpR2g0zV13hw8qjfoxDimkhbfAqM15n
zSZhrXO282e52YW0Xj5pQoJWd8CHkVU=

--B_3427811053_2167476--

From brian@innovationslab.net  Tue Aug 14 14:47:08 2012
Return-Path: <brian@innovationslab.net>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98B2621F87EA for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 14:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, 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 9GRN1llB1zYK for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 14:47:07 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id B268F21F85D1 for <mboned@ietf.org>; Tue, 14 Aug 2012 14:47:07 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 989F08809D; Tue, 14 Aug 2012 14:47:07 -0700 (PDT)
Received: from clemson.local (nat-gwifi.jhuapl.edu [128.244.87.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 28189130017; Tue, 14 Aug 2012 14:47:07 -0700 (PDT)
Message-ID: <502AC783.9040502@innovationslab.net>
Date: Tue, 14 Aug 2012 17:47:47 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 21:47:08 -0000

Why does T need to be 1?

Brian

On 8/14/12 5:43 PM, Lee, Yiu wrote:
> Hi Stig,
>
> Since we want T=1, this will not meet the "well-known" requirement defined
> in RFC4291. If we don't want to define a flag, what is the proper way to
> describe ffxx:8000::/20 and ffxx:0:8000::/96?
>
> Thanks,
> Yiu
>
>
> On 8/13/12 7:18 PM, "Stig Venaas" <stig@venaas.com> wrote:
>
>> On 13.08.2012 14:46, Brian Haberman wrote:
>>> On 8/13/12 4:21 PM, Behcet Sarikaya wrote:
>>>> Hi authors,
>>>>
>>>> Thanks for the revised draft, I find that the revision is in the right
>>>> direction.
>>>>
>>>> I am confused on the prefix lengths:
>>>> on Figure 2,
>>>> ffxx:8000:0:abc::/96
>>>> while in Section 3.1
>>>> ffxx:8000::/20
>>>>
>>>
>>> The x's correspond to the flags and scope fields within the multicast
>>> address.  Take a look at:
>>>
>>>
>>> http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-a
>>> ddresses.xml#ipv6-multicast-addresses-4
>>
>> We have one minor issue here though. They cannot simply be IANA
>> allocations, since they would not have the transient bit set. In
>> this case, the idea is that it should work for flag nibble values
>> like 1, 3 and 7. Actually I believe the transient bit should always
>> be set for these groups.
>>
>> Stig
>>
>>>
>>>
>>>> How come these are reserved prefixes?
>>>> What are the values that are reserved?
>>>>
>>>> If you look at RFC 6052, the unicast translation specification,
>>>> 64:ff9b::/96 is defined as the Well-Known Prefix. There are no x's in
>>>> the prefix definition.
>>>>
>>>> Regards,
>>>>
>>>> Behcet
>>>>
>>>> On Fri, Aug 10, 2012 at 1:49 AM,  <internet-drafts@ietf.org> wrote:
>>>>>
>>>>> 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           : IPv6 Multicast Address With Embedded IPv4
>>>>> Multicast Address
>>>>>           Author(s)       : Mohamed Boucadair
>>>>>                             Jacni Qin
>>>>>                             Yiu L. Lee
>>>>>                             Stig Venaas
>>>>>                             Xing Li
>>>>>                             Mingwei Xu
>>>>>           Filename        :
>>>>> draft-ietf-mboned-64-multicast-address-format-03.txt
>>>>>           Pages           : 13
>>>>>           Date            : 2012-08-09
>>>>>
>>>>> Abstract:
>>>>>      This document reserves two IPv6 multicast prefixes to be used in
>>>>> the
>>>>>      context of IPv4-IPv6 interconnection.  The document specifies an
>>>>>      algorithmic translation of an IPv6 multicast address to a
>>>>>      corresponding IPv4 multicast address, and vice versa.  This
>>>>>      algorithmic translation can be used in both IPv4-IPv6 translation
>>>>> or
>>>>>      encapsulation schemes.
>>>>>
>>>>>
>>>>>
>>>>> The IETF datatracker status page for this draft is:
>>>>>
>>>>> https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast-address
>>>>> -format
>>>>>
>>>>>
>>>>> There's also a htmlized version available at:
>>>>>
>>>>> http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-forma
>>>>> t-03
>>>>>
>>>>>
>>>>> A diff from the previous version is available at:
>>>>>
>>>>> http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-64-multicast-address
>>>>> -format-03
>>>>>
>>>>>
>>>>>
>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>
>>>>> _______________________________________________
>>>>> MBONED mailing list
>>>>> MBONED@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>> _______________________________________________
>>>> MBONED mailing list
>>>> MBONED@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>>
>>>
>>>
>>> _______________________________________________
>>> MBONED mailing list
>>> MBONED@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mboned
>>
>> _______________________________________________
>> MBONED mailing list
>> MBONED@ietf.org
>> https://www.ietf.org/mailman/listinfo/mboned


From stig@venaas.com  Tue Aug 14 18:32:17 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F79E21E80E2 for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 18:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 GDBxN5qXFaRL for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 18:32:16 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 62B4B21E80CD for <mboned@ietf.org>; Tue, 14 Aug 2012 18:32:16 -0700 (PDT)
Received: from [10.21.93.58] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id 38D657FF7; Wed, 15 Aug 2012 03:32:12 +0200 (CEST)
Message-ID: <502AFC5F.6000409@venaas.com>
Date: Tue, 14 Aug 2012 18:33:19 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com> <502AC783.9040502@innovationslab.net>
In-Reply-To: <502AC783.9040502@innovationslab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2012 01:32:17 -0000

On 14.08.2012 14:47, Brian Haberman wrote:
> Why does T need to be 1?

First of all, the idea is that it should work for SSM,
Embedded-RP and Prefix-based addresses. All of which have
T=1.

Also, it's not exactly like each address is allocated by
IANA for a specific purpose. I think it is correct to think
of these addresses as transient by nature.

Stig

> Brian
>
> On 8/14/12 5:43 PM, Lee, Yiu wrote:
>> Hi Stig,
>>
>> Since we want T=1, this will not meet the "well-known" requirement
>> defined
>> in RFC4291. If we don't want to define a flag, what is the proper way to
>> describe ffxx:8000::/20 and ffxx:0:8000::/96?
>>
>> Thanks,
>> Yiu
>>
>>
>> On 8/13/12 7:18 PM, "Stig Venaas" <stig@venaas.com> wrote:
>>
>>> On 13.08.2012 14:46, Brian Haberman wrote:
>>>> On 8/13/12 4:21 PM, Behcet Sarikaya wrote:
>>>>> Hi authors,
>>>>>
>>>>> Thanks for the revised draft, I find that the revision is in the right
>>>>> direction.
>>>>>
>>>>> I am confused on the prefix lengths:
>>>>> on Figure 2,
>>>>> ffxx:8000:0:abc::/96
>>>>> while in Section 3.1
>>>>> ffxx:8000::/20
>>>>>
>>>>
>>>> The x's correspond to the flags and scope fields within the multicast
>>>> address.  Take a look at:
>>>>
>>>>
>>>> http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-a
>>>>
>>>> ddresses.xml#ipv6-multicast-addresses-4
>>>
>>> We have one minor issue here though. They cannot simply be IANA
>>> allocations, since they would not have the transient bit set. In
>>> this case, the idea is that it should work for flag nibble values
>>> like 1, 3 and 7. Actually I believe the transient bit should always
>>> be set for these groups.
>>>
>>> Stig
>>>
>>>>
>>>>
>>>>> How come these are reserved prefixes?
>>>>> What are the values that are reserved?
>>>>>
>>>>> If you look at RFC 6052, the unicast translation specification,
>>>>> 64:ff9b::/96 is defined as the Well-Known Prefix. There are no x's in
>>>>> the prefix definition.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Behcet
>>>>>
>>>>> On Fri, Aug 10, 2012 at 1:49 AM,  <internet-drafts@ietf.org> wrote:
>>>>>>
>>>>>> 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           : IPv6 Multicast Address With Embedded IPv4
>>>>>> Multicast Address
>>>>>>           Author(s)       : Mohamed Boucadair
>>>>>>                             Jacni Qin
>>>>>>                             Yiu L. Lee
>>>>>>                             Stig Venaas
>>>>>>                             Xing Li
>>>>>>                             Mingwei Xu
>>>>>>           Filename        :
>>>>>> draft-ietf-mboned-64-multicast-address-format-03.txt
>>>>>>           Pages           : 13
>>>>>>           Date            : 2012-08-09
>>>>>>
>>>>>> Abstract:
>>>>>>      This document reserves two IPv6 multicast prefixes to be used in
>>>>>> the
>>>>>>      context of IPv4-IPv6 interconnection.  The document specifies an
>>>>>>      algorithmic translation of an IPv6 multicast address to a
>>>>>>      corresponding IPv4 multicast address, and vice versa.  This
>>>>>>      algorithmic translation can be used in both IPv4-IPv6
>>>>>> translation
>>>>>> or
>>>>>>      encapsulation schemes.
>>>>>>
>>>>>>
>>>>>>
>>>>>> The IETF datatracker status page for this draft is:
>>>>>>
>>>>>> https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast-address
>>>>>>
>>>>>> -format
>>>>>>
>>>>>>
>>>>>> There's also a htmlized version available at:
>>>>>>
>>>>>> http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-forma
>>>>>>
>>>>>> t-03
>>>>>>
>>>>>>
>>>>>> A diff from the previous version is available at:
>>>>>>
>>>>>> http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-64-multicast-address
>>>>>>
>>>>>> -format-03
>>>>>>
>>>>>>
>>>>>>
>>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>>
>>>>>> _______________________________________________
>>>>>> MBONED mailing list
>>>>>> MBONED@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>>> _______________________________________________
>>>>> MBONED mailing list
>>>>> MBONED@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> MBONED mailing list
>>>> MBONED@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>
>>> _______________________________________________
>>> MBONED mailing list
>>> MBONED@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mboned


From stig@venaas.com  Tue Aug 14 18:42:37 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A65C21E80E1 for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 18:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 ZzZor1GcI8w1 for <mboned@ietfa.amsl.com>; Tue, 14 Aug 2012 18:42:36 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 13B2F21E80CD for <mboned@ietf.org>; Tue, 14 Aug 2012 18:42:35 -0700 (PDT)
Received: from [10.21.93.58] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id F08307FF7; Wed, 15 Aug 2012 03:42:29 +0200 (CEST)
Message-ID: <502AFECA.1090905@venaas.com>
Date: Tue, 14 Aug 2012 18:43:38 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2012 01:42:37 -0000

On 14.08.2012 14:43, Lee, Yiu wrote:
> Hi Stig,
>
> Since we want T=1, this will not meet the "well-known" requirement defined
> in RFC4291. If we don't want to define a flag, what is the proper way to
> describe ffxx:8000::/20 and ffxx:0:8000::/96?

You could list them for all values of xx perhaps. I would maybe use
"x" and "y" and then discuss the allowed values.

There are scope relative allocations today, the main thing is that we
don't want to require the flags to be "0". Or maybe we want to require
the T-bit to be set. As I wrote earlier, I would think of these
addresses as transient, and T=1 is required for Embedded-RP etc.

The issue though is that if T=1, then it is not really an IANA
allocation as I see it, because IANA allocations have T=0. But if there
is IETF consensus, then one can still reserve these prefixes.

Stig

>
> Thanks,
> Yiu
>
>
> On 8/13/12 7:18 PM, "Stig Venaas" <stig@venaas.com> wrote:
>
>> On 13.08.2012 14:46, Brian Haberman wrote:
>>> On 8/13/12 4:21 PM, Behcet Sarikaya wrote:
>>>> Hi authors,
>>>>
>>>> Thanks for the revised draft, I find that the revision is in the right
>>>> direction.
>>>>
>>>> I am confused on the prefix lengths:
>>>> on Figure 2,
>>>> ffxx:8000:0:abc::/96
>>>> while in Section 3.1
>>>> ffxx:8000::/20
>>>>
>>>
>>> The x's correspond to the flags and scope fields within the multicast
>>> address.  Take a look at:
>>>
>>>
>>> http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-a
>>> ddresses.xml#ipv6-multicast-addresses-4
>>
>> We have one minor issue here though. They cannot simply be IANA
>> allocations, since they would not have the transient bit set. In
>> this case, the idea is that it should work for flag nibble values
>> like 1, 3 and 7. Actually I believe the transient bit should always
>> be set for these groups.
>>
>> Stig
>>
>>>
>>>
>>>> How come these are reserved prefixes?
>>>> What are the values that are reserved?
>>>>
>>>> If you look at RFC 6052, the unicast translation specification,
>>>> 64:ff9b::/96 is defined as the Well-Known Prefix. There are no x's in
>>>> the prefix definition.
>>>>
>>>> Regards,
>>>>
>>>> Behcet
>>>>
>>>> On Fri, Aug 10, 2012 at 1:49 AM,  <internet-drafts@ietf.org> wrote:
>>>>>
>>>>> 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           : IPv6 Multicast Address With Embedded IPv4
>>>>> Multicast Address
>>>>>           Author(s)       : Mohamed Boucadair
>>>>>                             Jacni Qin
>>>>>                             Yiu L. Lee
>>>>>                             Stig Venaas
>>>>>                             Xing Li
>>>>>                             Mingwei Xu
>>>>>           Filename        :
>>>>> draft-ietf-mboned-64-multicast-address-format-03.txt
>>>>>           Pages           : 13
>>>>>           Date            : 2012-08-09
>>>>>
>>>>> Abstract:
>>>>>      This document reserves two IPv6 multicast prefixes to be used in
>>>>> the
>>>>>      context of IPv4-IPv6 interconnection.  The document specifies an
>>>>>      algorithmic translation of an IPv6 multicast address to a
>>>>>      corresponding IPv4 multicast address, and vice versa.  This
>>>>>      algorithmic translation can be used in both IPv4-IPv6 translation
>>>>> or
>>>>>      encapsulation schemes.
>>>>>
>>>>>
>>>>>
>>>>> The IETF datatracker status page for this draft is:
>>>>>
>>>>> https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast-address
>>>>> -format
>>>>>
>>>>>
>>>>> There's also a htmlized version available at:
>>>>>
>>>>> http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-forma
>>>>> t-03
>>>>>
>>>>>
>>>>> A diff from the previous version is available at:
>>>>>
>>>>> http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-64-multicast-address
>>>>> -format-03
>>>>>
>>>>>
>>>>>
>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>
>>>>> _______________________________________________
>>>>> MBONED mailing list
>>>>> MBONED@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>> _______________________________________________
>>>> MBONED mailing list
>>>> MBONED@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>>
>>>
>>>
>>> _______________________________________________
>>> MBONED mailing list
>>> MBONED@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mboned
>>
>> _______________________________________________
>> MBONED mailing list
>> MBONED@ietf.org
>> https://www.ietf.org/mailman/listinfo/mboned


From yiu_lee@cable.comcast.com  Wed Aug 15 06:05:20 2012
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E558421F87D2 for <mboned@ietfa.amsl.com>; Wed, 15 Aug 2012 06:05:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.192
X-Spam-Level: 
X-Spam-Status: No, score=-104.192 tagged_above=-999 required=5 tests=[AWL=1.039, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_MED=-4, 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 ZUyWKK1eCDwn for <mboned@ietfa.amsl.com>; Wed, 15 Aug 2012 06:05:19 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 1ED5C21F87F8 for <mboned@ietf.org>; Wed, 15 Aug 2012 06:05:17 -0700 (PDT)
Received: from ([24.40.56.114]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.29371430; Wed, 15 Aug 2012 06:45:16 -0600
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.115]) by PACDCEXHUB01.cable.comcast.com ([fe80::84e8:95f3:f13b:169e%12]) with mapi id 14.02.0309.002; Wed, 15 Aug 2012 09:05:12 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Stig Venaas <stig@venaas.com>
Thread-Topic: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
Thread-Index: AQHNeuaa/IgIq3EAMUyq5pD/I66ROA==
Date: Wed, 15 Aug 2012 13:05:11 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD379D4563@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <502AFECA.1090905@venaas.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [24.40.55.70]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3427866310_2615048"
MIME-Version: 1.0
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2012 13:05:20 -0000

--B_3427866310_2615048
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

I like the idea to use x and y and explain the flag and scope in the
draft. As you said, we want to be flexible to support T=1, so this is not
a typical IANA allocation. If we get WG census to move forward, then we
can decide how to reserve these prefixes.


On 8/14/12 9:43 PM, "Stig Venaas" <stig@venaas.com> wrote:

>On 14.08.2012 14:43, Lee, Yiu wrote:
>> Hi Stig,
>>
>> Since we want T=1, this will not meet the "well-known" requirement
>>defined
>> in RFC4291. If we don't want to define a flag, what is the proper way to
>> describe ffxx:8000::/20 and ffxx:0:8000::/96?
>
>You could list them for all values of xx perhaps. I would maybe use
>"x" and "y" and then discuss the allowed values.
>
>There are scope relative allocations today, the main thing is that we
>don't want to require the flags to be "0". Or maybe we want to require
>the T-bit to be set. As I wrote earlier, I would think of these
>addresses as transient, and T=1 is required for Embedded-RP etc.
>
>The issue though is that if T=1, then it is not really an IANA
>allocation as I see it, because IANA allocations have T=0. But if there
>is IETF consensus, then one can still reserve these prefixes.
>
>Stig
>
>>
>> Thanks,
>> Yiu
>>
>>
>> On 8/13/12 7:18 PM, "Stig Venaas" <stig@venaas.com> wrote:
>>
>>> On 13.08.2012 14:46, Brian Haberman wrote:
>>>> On 8/13/12 4:21 PM, Behcet Sarikaya wrote:
>>>>> Hi authors,
>>>>>
>>>>> Thanks for the revised draft, I find that the revision is in the
>>>>>right
>>>>> direction.
>>>>>
>>>>> I am confused on the prefix lengths:
>>>>> on Figure 2,
>>>>> ffxx:8000:0:abc::/96
>>>>> while in Section 3.1
>>>>> ffxx:8000::/20
>>>>>
>>>>
>>>> The x's correspond to the flags and scope fields within the multicast
>>>> address.  Take a look at:
>>>>
>>>>
>>>> 
>>>>http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast
>>>>-a
>>>> ddresses.xml#ipv6-multicast-addresses-4
>>>
>>> We have one minor issue here though. They cannot simply be IANA
>>> allocations, since they would not have the transient bit set. In
>>> this case, the idea is that it should work for flag nibble values
>>> like 1, 3 and 7. Actually I believe the transient bit should always
>>> be set for these groups.
>>>
>>> Stig
>>>
>>>>
>>>>
>>>>> How come these are reserved prefixes?
>>>>> What are the values that are reserved?
>>>>>
>>>>> If you look at RFC 6052, the unicast translation specification,
>>>>> 64:ff9b::/96 is defined as the Well-Known Prefix. There are no x's in
>>>>> the prefix definition.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Behcet
>>>>>
>>>>> On Fri, Aug 10, 2012 at 1:49 AM,  <internet-drafts@ietf.org> wrote:
>>>>>>
>>>>>> 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           : IPv6 Multicast Address With Embedded
>>>>>>IPv4
>>>>>> Multicast Address
>>>>>>           Author(s)       : Mohamed Boucadair
>>>>>>                             Jacni Qin
>>>>>>                             Yiu L. Lee
>>>>>>                             Stig Venaas
>>>>>>                             Xing Li
>>>>>>                             Mingwei Xu
>>>>>>           Filename        :
>>>>>> draft-ietf-mboned-64-multicast-address-format-03.txt
>>>>>>           Pages           : 13
>>>>>>           Date            : 2012-08-09
>>>>>>
>>>>>> Abstract:
>>>>>>      This document reserves two IPv6 multicast prefixes to be used
>>>>>>in
>>>>>> the
>>>>>>      context of IPv4-IPv6 interconnection.  The document specifies
>>>>>>an
>>>>>>      algorithmic translation of an IPv6 multicast address to a
>>>>>>      corresponding IPv4 multicast address, and vice versa.  This
>>>>>>      algorithmic translation can be used in both IPv4-IPv6
>>>>>>translation
>>>>>> or
>>>>>>      encapsulation schemes.
>>>>>>
>>>>>>
>>>>>>
>>>>>> The IETF datatracker status page for this draft is:
>>>>>>
>>>>>> 
>>>>>>https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast-addre
>>>>>>ss
>>>>>> -format
>>>>>>
>>>>>>
>>>>>> There's also a htmlized version available at:
>>>>>>
>>>>>> 
>>>>>>http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-for
>>>>>>ma
>>>>>> t-03
>>>>>>
>>>>>>
>>>>>> A diff from the previous version is available at:
>>>>>>
>>>>>> 
>>>>>>http://www.ietf.org/rfcdiff?url2=draft-ietf-mboned-64-multicast-addre
>>>>>>ss
>>>>>> -format-03
>>>>>>
>>>>>>
>>>>>>
>>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>>
>>>>>> _______________________________________________
>>>>>> MBONED mailing list
>>>>>> MBONED@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>>> _______________________________________________
>>>>> MBONED mailing list
>>>>> MBONED@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> MBONED mailing list
>>>> MBONED@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>
>>> _______________________________________________
>>> MBONED mailing list
>>> MBONED@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mboned
>

--B_3427866310_2615048
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIVlwYJKoZIhvcNAQcCoIIViDCCFYQCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EzAwggUzMIIEG6ADAgECAhBTm5vcGTrcIPdnvVTe3rDkMA0GCSqGSIb3DQEBBQUAMIGTMQsw
CQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxm
b3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVu
dCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTEyMDIxNDAwMDAwMFoX
DTEzMDIxMzIzNTk1OVowKjEoMCYGCSqGSIb3DQEJARYZeWl1X2xlZUBjYWJsZS5jb21jYXN0
LmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANOm2q1Oat5U5a79IA1Yx+oa
djvccI4HQYLkQtDXj9an1bz7JT52yBADiZJ42pTJ35L4yPzYRY/4b1k7RCsodmRzu4F2n1wA
Xjg3hkRygwiAVrEv7p1FM4Wsr4nY6utC6/dhrJFkTtLzMmQXcSeVF1gpoaDKzf9UNvXNZCy8
dpLhdP4v8t7JOhfPyR3LBOo7vKk4WIv7ugGVgyLXwGSwu0rEVNOwLtPdoTJW0pi+ATaJeAuf
WVIKLRVjK56vKBeA3ms3BJNOp5zkfAk5j3IymZZMD156Tib5ViL8dCTycYZyMNWBOrDPC/yn
c4itE6q05Wh94QYGp6GcsZkiHEXFZrUCAwEAAaOCAekwggHlMB8GA1UdIwQYMBaAFHoTTgB0
W8Z4Y2QnwS/ioFu8ecV7MB0GA1UdDgQWBBTdz82GEvcyRLU/wx9KzuYvjgUddzAOBgNVHQ8B
Af8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQED
BQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYI
KwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMFcGA1UdHwRQME4wTKBK
oEiGRmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9u
YW5kU2VjdXJlRW1haWxDQS5jcmwwgYgGCCsGAQUFBwEBBHwwejBSBggrBgEFBQcwAoZGaHR0
cDovL2NydC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1
cmVFbWFpbENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuY29tb2RvY2EuY29tMCQG
A1UdEQQdMBuBGXlpdV9sZWVAY2FibGUuY29tY2FzdC5jb20wDQYJKoZIhvcNAQEFBQADggEB
AFeEfwmWgj/jpA3+ctSoBsbvHGnWLz00p8NBX2+qzz8QjgDpZT5T1Fux5MV6qlVJpND12pzq
ziUyFCBdv6QOMyiOrn5RxooXY9W6Hpa8qBD4v9BXy5qtP7gi4xJhFufXdNZXEw2RwNyjBzfV
/F2Q8HSwlyOwS+fHKYZZ9gy/KneVP//YcrC4icG1ipJQ2+gCUs+uUAouz0xF0uBYE/bQRTss
oRTY6D/X5lxarw28oocfr38v4Ro5bmsZlsEF22OvpKZX5tfz1aOL5U9nhXixY7Sd9B9BGHl7
mrybVUl7NnguWGIAhHiVD9ce1u4jJ1PnNmrNkvwJouS/7zYCId8000cwggUaMIIEAqADAgEC
AhBtGeqnGU9qMyLmIjJ6qnHeMA0GCSqGSIb3DQEBBQUAMIGuMQswCQYDVQQGEwJVUzELMAkG
A1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRS
VVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UE
AxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMB4XDTEx
MDQyODAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJH
cmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD
QSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBT
ZWN1cmUgRW1haWwgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCShIRbS1eY
1F4vi6ThQMijU1hfZmXxMk73nzJ9VdB4TFW3QpTg+SdxB8XGaaS5MsTxQBqQzCdWYn8XtXFp
ruUgG+TLY15gyqJB9mrho/+43x9IbWVDjCouK2M4d9+xF6zC2oIC1tQyatRnbyATj1w1+uVU
gK/YcQodNwoCUFNslR2pEBS0mZVZEjH/CaLSTNxS297iQAFbSGjdxUq04O0kHzqvcV8H46y/
FDuwJXFoPfQP1hdYRhWBPGiLi4MPbXohV+Y0sNsyfuNK4aVScmQmkU6lkg//4LFg/RpvaFGZ
Y40ai6XMQpubfSJj06mg/M6ekN9EGfRcWzW6FvOnm//BAgMBAAGjggFLMIIBRzAfBgNVHSME
GDAWgBSJgmd9xJ0mcABLtFBIfN49rgRufTAdBgNVHQ4EFgQUehNOAHRbxnhjZCfBL+KgW7x5
xXswDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8CAQAwEQYDVR0gBAowCDAGBgRV
HSAAMFgGA1UdHwRRME8wTaBLoEmGR2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9VVE4tVVNF
UkZpcnN0LUNsaWVudEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMHQGCCsGAQUFBwEBBGgw
ZjA9BggrBgEFBQcwAoYxaHR0cDovL2NydC51c2VydHJ1c3QuY29tL1VUTkFkZFRydXN0Q2xp
ZW50X0NBLmNydDAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTANBgkq
hkiG9w0BAQUFAAOCAQEAhda+eFdVbTN/RFL+QtUGqAEDgIr7DbL9Sr/2r0FJ9RtaxdKtG3Nu
PukmfOZMmMEwKN/L+0I8oSU+CnXW0D05hmbRoZu1TZtvryhsHa/l6nRaqNqxwPF1ei+eupN5
yv7ikR5WdLL4jdPgQ3Ib7Y/9YDkgR/uLrzplSDyYPaUlv73vYOBJ5RbI6z9Dg/Dg7g3B080z
X5vQvWBqszv++tTJOjwf7Zv/m0kzvkIpOYPuM2kugp1FTahp2oAbHj3SGl18R5mlmwhtEpmG
1l1XBxunML5LSUS4kH7K0Xk467Qz+qA6XSZYnmFVGLQh1ZnV4ENAQjC+6qXnlNKw/vN1+X9u
5zCCBJ0wggOFoAMCAQICEDQ96SusJzT/j8s0lPvMcFQwDQYJKoZIhvcNAQEFBQAwbzELMAkG
A1UEBhMCU0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRl
cm5hbCBUVFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAe
Fw0wNTA2MDcwODA5MTBaFw0yMDA1MzAxMDQ4MzhaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UE
CBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNU
IE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMt
VVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxq
mNVNNRm5pELlzkniii8efNIxB8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPM
yaQylbsMTzC9mKALi+VuG6JG+ni8om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbN
oKXqvgvOdjp6Dpvq/NonWz1zHyLmSGHGTPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcR
Wdq6hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7NlyP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/
MLbu9mIwFIws6wIDAQABo4H0MIHxMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1Qa
MB0GA1UdDgQWBBSJgmd9xJ0mcABLtFBIfN49rgRufTAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0T
AQH/BAUwAwEB/zARBgNVHSAECjAIMAYGBFUdIAAwRAYDVR0fBD0wOzA5oDegNYYzaHR0cDov
L2NybC51c2VydHJ1c3QuY29tL0FkZFRydXN0RXh0ZXJuYWxDQVJvb3QuY3JsMDUGCCsGAQUF
BwEBBCkwJzAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTANBgkqhkiG
9w0BAQUFAAOCAQEAAbyc42MosPMxAcLfe91ioAGdIzEPnJJzU1HqH0z61p/Eyi9nfngzD3QW
uZGHkfWKJvpkcADYHvkLBGJQh5OB1Nr1I9s0u4VWtHA0bniDNx6FHMURFZJfhxe9rGr98cLR
zIlfsXzwPlHyNfN87GCYazor4O/fs32G67Ub9VvsonyYE9cAULnRLXPeA3h04QWFMV7Lmrmd
lMa5lDd1ctxE+2fo8PolHlKn2iXpR+CgxzygTrEKNvt3SJ/vl4r7tP7jlBSog7xcLT/SYHFg
7sJxggzpiDbj2iC0o6BsqpZLuICOdcpJB/Y7FLrf3AXZn9vgsuZNoHgm5+ctbn9fxh6IFTCC
BDYwggMeoAMCAQICAQEwDQYJKoZIhvcNAQEFBQAwbzELMAkGA1UEBhMCU0UxFDASBgNVBAoT
C0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBUVFAgTmV0d29yazEi
MCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAeFw0wMDA1MzAxMDQ4MzhaFw0y
MDA1MzAxMDQ4MzhaMG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQG
A1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0
IEV4dGVybmFsIENBIFJvb3QwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC39xoz
5vIABC054E5b7R+8bA/Ntfojts7emxEzl6QpTH2Tn71KvJPtAxrjj8/lbVBa1pcplFqAsEl6
2y6V/bjKvzc4LR4+kUGtcFbH8E8/6DKedMrIkFTpxl8PeJ2aQDwOrGGqXhSPnoehalDc15pO
rwWzpnGUnHGzUGAKxxOdOAeGAqjpqGkmGJCrTLBPI6s6T4TY386f4Wlvu9dC12tE5Met7m1B
X3JacQg3s3llpFmglDf3AC8NwpJy2tA4ctsUqEXEXSp9t7TWxO6szRNEt8kr3UMAJfphuWlq
WCMRt6czj1Z1WfXNKddGtworZbbTQm8Vsrh7++/pXVPVNFonAgMBAAGjgdwwgdkwHQYDVR0O
BBYEFK29mHo0tCb3+sQmVO8DveAky1QaMAsGA1UdDwQEAwIBBjAPBgNVHRMBAf8EBTADAQH/
MIGZBgNVHSMEgZEwgY6AFK29mHo0tCb3+sQmVO8DveAky1QaoXOkcTBvMQswCQYDVQQGEwJT
RTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRU
UCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290ggEBMA0GCSqG
SIb3DQEBBQUAA4IBAQCwm+CFJcLWI+IPlgaSnUGYnNmEeYHZHlsUByM2ZY+w2He7rEFsR2CD
UbD5Mj3n/PYmE8eAFqW/WvyHz3h5iSGa4kwHCoY1vPLeUcTSlrfcfk7ucP0cOesMAlEULY69
FuDB30Z15ySt7PRCtIWTcBBnup0GNUoY0yt6zFFCoXpj0ea7ocUrwja+Ew3mvWN+eXunCQ1A
q2rdj4rD9vaMGkIFUdRF9Z+nYiFoFSBDPJnnfL0k2KmRF3OIP1YbMTgYtHEPms3IDp6OLhvh
jJiDyx8x8URMxgRzSXZgD8f4vReAay7pzEwOWpp5DyAKLtWeYyYeVZKU2IIXWnvQvMePToYE
MYICLzCCAisCAQEwgagwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNo
ZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkw
NwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwg
Q0ECEFObm9wZOtwg92e9VN7esOQwCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJBDEWBBQ41VQJ
+2DaXUuNqga/nWvdpu+3hzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ
BTEPFw0xMjA4MTUxMzA1MDlaMA0GCSqGSIb3DQEBAQUABIIBAD2zlNEfCxuIxo/iEDvD15Hc
1enzluszh7pHJ1/fqu0Sucvna16TWQkqtS2wniPYPJ+cfyWQUUkMSK9t/E9571jn3JOPbNt4
1HnqY8OF9IhLvcjIpQ50ctNJVbjFWXMOGTAvzRGzRfj5zc+dJtqpb9xezvzFrpUcg0pjJOT7
uSweifUoMrUKk6oLhUa/Ybd10dwff5BiaNAgvS3QPM1g2GcpDknqrDqmpsJ05S23POl4AGO1
PIPF6anB5q/dM18omu4AXzO9+CXzyxhXf5pWs2Xuvzl01Z4HqHyx0cKLfJOQEmm4Wi6YkTTM
ELFz8D1h1zdf8axJI/G8aYH0DAz4pp8=

--B_3427866310_2615048--

From mohamed.boucadair@orange.com  Wed Aug 15 22:55:27 2012
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E61AC21F844F for <mboned@ietfa.amsl.com>; Wed, 15 Aug 2012 22:55:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.035
X-Spam-Level: 
X-Spam-Status: No, score=-2.035 tagged_above=-999 required=5 tests=[AWL=0.213,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N-3BlFUx03Xa for <mboned@ietfa.amsl.com>; Wed, 15 Aug 2012 22:55:26 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id CED2021F844E for <mboned@ietf.org>; Wed, 15 Aug 2012 22:55:25 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 251E4324276; Thu, 16 Aug 2012 07:55:25 +0200 (CEST)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 0AFC34C015; Thu, 16 Aug 2012 07:55:25 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Thu, 16 Aug 2012 07:55:07 +0200
From: <mohamed.boucadair@orange.com>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>, Stig Venaas <stig@venaas.com>
Date: Thu, 16 Aug 2012 07:55:06 +0200
Thread-Topic: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
Thread-Index: Ac16PYN273/6hs4GReGltv8h/E17qQBNhO3Q
Message-ID: <94C682931C08B048B7A8645303FDC9F36E4FC2D9E2@PUEXCB1B.nanterre.francetelecom.fr>
References: <CAC8QAcdJ-u_XrWQ=soNL9rMykMD4W4oxsZrGDBdFcMU8t2ebqg@mail.gmail.com> <502975B9.30403@innovationslab.net> <50298B3E.2020207@venaas.com> <CAC8QAcc4V3x=AG+XC-bOupkKzyfOTJDR2b=RBiJBgojd7A9LaA@mail.gmail.com>
In-Reply-To: <CAC8QAcc4V3x=AG+XC-bOupkKzyfOTJDR2b=RBiJBgojd7A9LaA@mail.gmail.com>
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: 2012.8.16.22416
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 05:55:27 -0000

Hi Behcet,

I updated my local copy to take into account your comment. Thanks.

Cheers,
Med=20

>-----Message d'origine-----
>De : mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org]=20
>De la part de Behcet Sarikaya
>Envoy=E9 : mardi 14 ao=FBt 2012 18:55
>=C0 : Stig Venaas
>Cc : mboned@ietf.org
>Objet : Re: [MBONED]=20
>draft-ietf-mboned-64-multicast-address-format-03.txt
>
>On Mon, Aug 13, 2012 at 6:18 PM, Stig Venaas <stig@venaas.com> wrote:
>> On 13.08.2012 14:46, Brian Haberman wrote:
>>>
>>> On 8/13/12 4:21 PM, Behcet Sarikaya wrote:
>>>>
>>>> Hi authors,
>>>>
>>>> Thanks for the revised draft, I find that the revision is=20
>in the right
>>>> direction.
>>>>
>>>> I am confused on the prefix lengths:
>>>> on Figure 2,
>>>> ffxx:8000:0:abc::/96
>>>> while in Section 3.1
>>>> ffxx:8000::/20
>>>>
>>>
>>> The x's correspond to the flags and scope fields within the=20
>multicast
>>> address.  Take a look at:
>>>
>>>
>>>=20
>http://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-m
>ulticast-addresses.xml#ipv6-multicast-addresses-4
>>
>>
>> We have one minor issue here though. They cannot simply be IANA
>> allocations, since they would not have the transient bit set. In
>> this case, the idea is that it should work for flag nibble values
>> like 1, 3 and 7. Actually I believe the transient bit should always
>> be set for these groups.
>
>I think it will be better to clarify in the draft saying that xx
>corresponds to flgs and scop fields defined in RFC 3306.
>
>Regards,
>
>Behcet
>
>>
>> Stig
>>
>>
>>>
>>>
>>>> How come these are reserved prefixes?
>>>> What are the values that are reserved?
>>>>
>>>> If you look at RFC 6052, the unicast translation specification,
>>>> 64:ff9b::/96 is defined as the Well-Known Prefix. There=20
>are no x's in
>>>> the prefix definition.
>>>>
>>>> Regards,
>>>>
>>>> Behcet
>>>>
>>>> On Fri, Aug 10, 2012 at 1:49 AM,  <internet-drafts@ietf.org> wrote:
>>>>>
>>>>>
>>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>>> directories.
>>>>>   This draft is a work item of the MBONE Deployment=20
>Working Group of
>>>>> the IETF.
>>>>>
>>>>>          Title           : IPv6 Multicast Address With=20
>Embedded IPv4
>>>>> Multicast Address
>>>>>          Author(s)       : Mohamed Boucadair
>>>>>                            Jacni Qin
>>>>>                            Yiu L. Lee
>>>>>                            Stig Venaas
>>>>>                            Xing Li
>>>>>                            Mingwei Xu
>>>>>          Filename        :
>>>>> draft-ietf-mboned-64-multicast-address-format-03.txt
>>>>>          Pages           : 13
>>>>>          Date            : 2012-08-09
>>>>>
>>>>> Abstract:
>>>>>     This document reserves two IPv6 multicast prefixes to=20
>be used in the
>>>>>     context of IPv4-IPv6 interconnection.  The document=20
>specifies an
>>>>>     algorithmic translation of an IPv6 multicast address to a
>>>>>     corresponding IPv4 multicast address, and vice versa.  This
>>>>>     algorithmic translation can be used in both IPv4-IPv6=20
>translation or
>>>>>     encapsulation schemes.
>>>>>
>>>>>
>>>>>
>>>>> The IETF datatracker status page for this draft is:
>>>>>
>>>>>=20
>https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast
>-address-format
>>>>>
>>>>>
>>>>> There's also a htmlized version available at:
>>>>>
>>>>>=20
>http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-addre
>ss-format-03
>>>>>
>>>>>
>>>>> A diff from the previous version is available at:
>>>>>
>>>>>=20
>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mboned-64-multicast
>-address-format-03
>>>>>
>>>>>
>>>>>
>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>
>>>>> _______________________________________________
>>>>> MBONED mailing list
>>>>> MBONED@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>>
>>>> _______________________________________________
>>>> MBONED mailing list
>>>> MBONED@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mboned
>>>>
>>>
>>>
>>> _______________________________________________
>>> MBONED mailing list
>>> MBONED@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mboned
>>
>>
>> _______________________________________________
>> MBONED mailing list
>> MBONED@ietf.org
>> https://www.ietf.org/mailman/listinfo/mboned
>_______________________________________________
>MBONED mailing list
>MBONED@ietf.org
>https://www.ietf.org/mailman/listinfo/mboned
>=

From mohamed.boucadair@orange.com  Wed Aug 15 23:00:07 2012
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E419721F846D for <mboned@ietfa.amsl.com>; Wed, 15 Aug 2012 23:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.039
X-Spam-Level: 
X-Spam-Status: No, score=-2.039 tagged_above=-999 required=5 tests=[AWL=0.209,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MNnHkz-jMMfs for <mboned@ietfa.amsl.com>; Wed, 15 Aug 2012 23:00:07 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id C97F421F846C for <mboned@ietf.org>; Wed, 15 Aug 2012 23:00:06 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id 3AA5C2DC350; Thu, 16 Aug 2012 08:00:06 +0200 (CEST)
Received: from PUEXCH61.nanterre.francetelecom.fr (unknown [10.101.44.32]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 1CC73238048; Thu, 16 Aug 2012 08:00:06 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH61.nanterre.francetelecom.fr ([10.101.44.32]) with mapi; Thu, 16 Aug 2012 07:59:48 +0200
From: <mohamed.boucadair@orange.com>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>, Stig Venaas <stig@venaas.com>
Date: Thu, 16 Aug 2012 07:59:47 +0200
Thread-Topic: [MBONED] draft-ietf-mboned-64-multicast-address-format
Thread-Index: Ac16WA8s5Z4mjAHBTgSfqlOTDHx8+ABG7CZA
Message-ID: <94C682931C08B048B7A8645303FDC9F36E4FC2D9E3@PUEXCB1B.nanterre.francetelecom.fr>
References: <94C682931C08B048B7A8645303FDC9F36E4FC2D8C2@PUEXCB1B.nanterre.francetelecom.fr> <CAC8QAccH-72K7P3fj-uJB7x5L9xYsLF3W6xXATdtXrT6HB8Krw@mail.gmail.com> <502A821A.6080901@venaas.com> <CAC8QAcd2JP=H5_eXRhtoSoz6ytnV=oUqDWOot4j_THM3M5Ak_A@mail.gmail.com>
In-Reply-To: <CAC8QAcd2JP=H5_eXRhtoSoz6ytnV=oUqDWOot4j_THM3M5Ak_A@mail.gmail.com>
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: 2012.6.19.115414
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 06:00:08 -0000

Re-,

Please see inline.

Cheers,
Med=20

>-----Message d'origine-----
>De : mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org]=20
>De la part de Behcet Sarikaya
>Envoy=E9 : mardi 14 ao=FBt 2012 22:05
>=C0 : Stig Venaas
>Cc : MBONED WG
>Objet : Re: [MBONED] draft-ietf-mboned-64-multicast-address-format
>
>On Tue, Aug 14, 2012 at 11:51 AM, Stig Venaas <stig@venaas.com> wrote:
>> On 8/14/2012 9:40 AM, Behcet Sarikaya wrote:
>>>
>>> On Tue, Aug 14, 2012 at 4:09 AM, =20
><mohamed.boucadair@orange.com> wrote:
>>>>
>>>> Dear all,
>>>>
>>>> I'm initiating this thread in the hope of understanding the
>>>> objections from the 6man WG and hopefully to make some progress for
>>>> this document.  To initiate the discussion, below are provided some
>>>> preliminary Q/A:
>>>>
>>>> What is the scope of this document?
>>>>     The document specifies an algorithmic translation of an IPv6
>>>>     multicast address to a corresponding IPv4 multicast=20
>address, and
>>>>     vice versa.  The document reserves two IPv6 multicast=20
>prefixes to
>>>>     be used for that purpose.
>>>>
>>>> What are these reserved prefixes?
>>>>     *  ff3x:0:8000::/96 for SSM
>>>>     *  ffxx:8000::/20 for ASM
>>>>
>>>> Does this document update IPv6 addressing architecture?
>>>>     No.
>>>>
>>>> Is there a unicast counterpart of this proposal?
>>>>     Yes, RFC6052.
>>>>
>>>> What is the problem to be solved?
>>>>     There are several use cases as detailed in=20
>[I-D.ietf-mboned-v4v6-
>>>>     mcast-ps].  In particular, the following use cases are of
>>>>     interest:
>>>>     1.  An IPv6-only receiver wants to receive multicast=20
>content from
>>>>         an IPv4-only source (6-4).
>>>>     2.  An IPv4 receiver wants to join a multicast group in IPv4
>>>>         domain via an IPv6-only network (4-6-4).
>>>>
>>>> Are there solutions for the unicast counterpart of these use cases?
>>>>     Yes; various solutions including:
>>>>     1.  6-4: RFC6146
>>>>     2.  4-6-4: RFC6333, RFC6346, ...
>>>
>>>
>>>
>>> I don't understand why RFC 6333 is included here.
>>> If you take a look at
>>>=20
>http://tools.ietf.org/html/draft-sarikaya-softwire-dslitemulticast-01
>>> there is no need for this draft.
>>
>>
>> If I understand your draft correctly, it uses unicast for the
>> encapsulation, then there is no need for this.
>>
>> But e.g. draft-ietf-softwire-dslite-multicast-02 needs it. If you are
>> using multicast encapsulation (4 in 6), you need to know=20
>which group G
>> or (S,G) to join at the tunnel egress point. And at the ingress, you
>> need to interpret the IPv6 join you receive and extract the=20
>IPv4 address
>> to know which IPv4 group is requested. For the latter part you could
>> possibly encapsulate the joins, but I think that is not so=20
>good. Anyway,
>> you need it for the first part.
>>
>> Encapsulation is very similar to translation. The only real=20
>difference
>> I see, is that when you receive packets at the egress, you=20
>can just do
>> decap, you don't need to figure out what the addresses in=20
>the new header
>> should be.
>
>First of all as Mboned chair said, multicast can be tunneled, i.e.
>encapsulated. AMT is an example. DS-Lite tunnel as in
>draft-sarikaya-softwire-dslitemulticast-01 is another example.

Med: this is a unicast-based solution between the CPE and the aftr. You hav=
e presented this draft is softwire and the group preferred a solution makin=
g use of native multicast capabilities to deliver IPv4 multicast over an IP=
v6 network.

>
>The point here is that draft-ietf-mboned-64-multicast-address-format
>describes part of translation multicast and it should be explained as
>such. Encapsulation or tunneling has nothing to do with it.
>

Med: draft-ietf-mboned-64-multicast-address-format specifies address transl=
ation algorithm but it does not assumption on the deployment context. As su=
ch, this address translation can be used in scenarios where multicast data =
is encapsulated or translated. Specific solution design is out of scope of =
this document.


>Hope this clarifies my point and we don't keep coming back to=20
>this again.
>
>Regards,
>
>Behcet
>_______________________________________________
>MBONED mailing list
>MBONED@ietf.org
>https://www.ietf.org/mailman/listinfo/mboned
>=

From sarikaya2012@gmail.com  Thu Aug 16 14:47:56 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB40121F84F3 for <mboned@ietfa.amsl.com>; Thu, 16 Aug 2012 14:47:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.562
X-Spam-Level: 
X-Spam-Status: No, score=-3.562 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JvSlO0cwhgpC for <mboned@ietfa.amsl.com>; Thu, 16 Aug 2012 14:47:56 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4DAB821F84D2 for <mboned@ietf.org>; Thu, 16 Aug 2012 14:47:56 -0700 (PDT)
Received: by iabz21 with SMTP id z21so610535iab.31 for <mboned@ietf.org>; Thu, 16 Aug 2012 14:47:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=XiUYeUx8uc2w+iFPYGtuY03x/PTwkg+2oUKlzAHiBDg=; b=UgWgFcrEvgjSfJXBwhR0G9cTErtkQ/3yjPux/KspgQRevFxbro/Yb5ebR1oL3u/Ltz TePiCtjuFdGu85YoZ2eCHGI2dRtF7EYbjysk2VUgHEfdqaLNYd6/ixvnoExALDgBMfYo r89iqoND+PlGIAwJKfn/Pd3ROf7lq3pzfxNN6pionc41JNfSZm90INPm02U4JY7+rikc BdYZml9w0kmERrHaMOO7y3VM5x4++K9yJ8XjnoINq/mKZ6/OgKRdXmAPtUix2pXnPaFh +bxN12h7Icdoeasht/15QnOpMe6+apJ2SeOPNXVWAct2Kg4Hy3uhPb6SFlewQl3KuWI8 QygA==
MIME-Version: 1.0
Received: by 10.42.31.5 with SMTP id x5mr2593668icc.40.1345153675734; Thu, 16 Aug 2012 14:47:55 -0700 (PDT)
Received: by 10.231.55.70 with HTTP; Thu, 16 Aug 2012 14:47:55 -0700 (PDT)
In-Reply-To: <502AB938.10301@venaas.com>
References: <94C682931C08B048B7A8645303FDC9F36E4FC2D8C2@PUEXCB1B.nanterre.francetelecom.fr> <CAC8QAccH-72K7P3fj-uJB7x5L9xYsLF3W6xXATdtXrT6HB8Krw@mail.gmail.com> <502A821A.6080901@venaas.com> <CAC8QAcd2JP=H5_eXRhtoSoz6ytnV=oUqDWOot4j_THM3M5Ak_A@mail.gmail.com> <502AB938.10301@venaas.com>
Date: Thu, 16 Aug 2012 16:47:55 -0500
Message-ID: <CAC8QAcfx38=uKi-3tqSsGR1wwDOA6L_hg7f1mJRAe+sf78HcrA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Stig Venaas <stig@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 21:47:56 -0000

> Yes, and I'm trying to explain why this solution applies to
> tunneling. draft-ietf-softwire-dslite-multicast-02 is one example.
>

Let that draft explain it not the address format draft.

>
>> The point here is that draft-ietf-mboned-64-multicast-address-format
>> describes part of translation multicast and it should be explained as
>> such. Encapsulation or tunneling has nothing to do with it.
>
>
> And I was trying to explain above why it is also part of encapsulation.
>

That is hopeless.

Behcet

From tjc@ecs.soton.ac.uk  Thu Aug 16 16:11:47 2012
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8872411E80A4 for <mboned@ietfa.amsl.com>; Thu, 16 Aug 2012 16:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level: 
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[AWL=-0.398, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cb+js+INoknY for <mboned@ietfa.amsl.com>; Thu, 16 Aug 2012 16:11:46 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 57C8221E803C for <mboned@ietf.org>; Thu, 16 Aug 2012 16:11:46 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q7GNBek2021021 for <mboned@ietf.org>; Fri, 17 Aug 2012 00:11:40 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk q7GNBek2021021
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1345158700; bh=e/+FfJ5IFhhR6/l/s6Gx91GFEWI=; h=Subject:References:From:In-Reply-To:Date:To:Mime-Version; b=YwQQYu2/2OTm9CKtqGL0UX4260StGJEoSpIyLVT2irG1xW0rH31x5cv/6b3AIREHz bpIjblDBeqpKlqfOARSt89zuULr1C3PU/wQZeGr3s7jFlHXcG8gUs8UeeOS925rzgk 9Wg3T+u2fS++k3LQGsZrF8EvhkLL2VekYBVtRVLE=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id o7G0Be0430601481Hu ret-id none; Fri, 17 Aug 2012 00:11:40 +0100
Received: from [192.168.1.101] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q7GNBZRn003335 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <mboned@ietf.org>; Fri, 17 Aug 2012 00:11:36 +0100
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com> <502AFECA.1090905@venaas.com> <2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk>
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=us-ascii
X-Mailer: iPad Mail (9B206)
In-Reply-To: <502AFECA.1090905@venaas.com>
Message-ID: <EMEW3|1c3fd9d33484c5343b2d7337b5211574o7G0Be03tjc|ecs.soton.ac.uk|2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk>
Date: Fri, 17 Aug 2012 00:12:01 +0100
To: "mboned@ietf.org" <mboned@ietf.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=o7G0Be043060148100; tid=o7G0Be0430601481Hu; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: q7GNBek2021021
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 23:11:47 -0000

On 15 Aug 2012, at 02:43, Stig Venaas <stig@venaas.com> wrote:

> On 14.08.2012 14:43, Lee, Yiu wrote:
>> Hi Stig,
>>=20
>> Since we want T=3D1, this will not meet the "well-known" requirement defi=
ned
>> in RFC4291. If we don't want to define a flag, what is the proper way to
>> describe ffxx:8000::/20 and ffxx:0:8000::/96?
>=20
> You could list them for all values of xx perhaps. I would maybe use
> "x" and "y" and then discuss the allowed values.
>=20
> There are scope relative allocations today, the main thing is that we
> don't want to require the flags to be "0". Or maybe we want to require
> the T-bit to be set. As I wrote earlier, I would think of these
> addresses as transient, and T=3D1 is required for Embedded-RP etc.
>=20
> The issue though is that if T=3D1, then it is not really an IANA
> allocation as I see it, because IANA allocations have T=3D0. But if there
> is IETF consensus, then one can still reserve these prefixes.

I agree with Stig; there are multiple prefixes being reserved here.

The text is effectively updating both RFC3306 and RFC3956 since the above pr=
efix is setting a bit in the reserved bit range of both those specifications=
.  RFC3306 also says all those reserved bits (17-24) must be zero, while RFC=
3956 doesn't explicitly say that for bits 17-20 (it probably should, if you'=
re now using one of those bits).

Both RFCs say that if R or P flags are set, then T must be set too, so I'm n=
ot sure you have freedom to say "if T=3D1" if you want to support those two m=
ethods.=20

Finally, it may make more sense to use ffxx:1000::/20 for ASM, and thus only=
 use the rightmost bit of the four reserved bits (for RFC3956 at least)?

Tim=

From stig@venaas.com  Fri Aug 17 11:06:27 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ADE221F8442 for <mboned@ietfa.amsl.com>; Fri, 17 Aug 2012 11:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.467
X-Spam-Level: 
X-Spam-Status: No, score=-102.467 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nvQiReXcJmf3 for <mboned@ietfa.amsl.com>; Fri, 17 Aug 2012 11:06:26 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id 0EFA221F8441 for <mboned@ietf.org>; Fri, 17 Aug 2012 11:06:26 -0700 (PDT)
Received: from [IPv6:2001:420:301:1004:3090:6830:dbf9:beb7] (unknown [IPv6:2001:420:301:1004:3090:6830:dbf9:beb7]) by ufisa.uninett.no (Postfix) with ESMTPSA id BB1CB7FE7 for <mboned@ietf.org>; Fri, 17 Aug 2012 20:06:23 +0200 (CEST)
Message-ID: <502E8819.5030901@venaas.com>
Date: Fri, 17 Aug 2012 11:06:17 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: mboned@ietf.org
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com> <502AFECA.1090905@venaas.com> <2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <EMEW3|1c3fd9d33484c5343b2d7337b5211574o7G0Be03tjc|ecs.soton.ac.uk|2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|1c3fd9d33484c5343b2d7337b5211574o7G0Be03tjc|ecs.soton.ac.uk|2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 18:06:27 -0000

Hi Tim

On 8/16/2012 4:12 PM, Tim Chown wrote:
> On 15 Aug 2012, at 02:43, Stig Venaas <stig@venaas.com> wrote:
>
>> On 14.08.2012 14:43, Lee, Yiu wrote:
>>> Hi Stig,
>>>
>>> Since we want T=1, this will not meet the "well-known" requirement defined
>>> in RFC4291. If we don't want to define a flag, what is the proper way to
>>> describe ffxx:8000::/20 and ffxx:0:8000::/96?
>>
>> You could list them for all values of xx perhaps. I would maybe use
>> "x" and "y" and then discuss the allowed values.
>>
>> There are scope relative allocations today, the main thing is that we
>> don't want to require the flags to be "0". Or maybe we want to require
>> the T-bit to be set. As I wrote earlier, I would think of these
>> addresses as transient, and T=1 is required for Embedded-RP etc.
>>
>> The issue though is that if T=1, then it is not really an IANA
>> allocation as I see it, because IANA allocations have T=0. But if there
>> is IETF consensus, then one can still reserve these prefixes.
>
> I agree with Stig; there are multiple prefixes being reserved here.
>
> The text is effectively updating both RFC3306 and RFC3956 since the above prefix is setting a bit in the reserved bit range of both those specifications.  RFC3306 also says all those reserved bits (17-24) must be zero, while RFC3956 doesn't explicitly say that for bits 17-20 (it probably should, if you're now using one of those bits).

You're right about 3306. I wonder now if instead of practically
reserving a specific value for the entire nibble of remaining
reserved bits in 3306, it would be better to reserve just one of
the bits. I don't think it updates 3956, because it doesn't talk
about those bits at all, AFAICT.

> Both RFCs say that if R or P flags are set, then T must be set too, so I'm not sure you have freedom to say "if T=1" if you want to support those two methods.

Yes, that's why I've been saying that we can't just get an IANA
allocation. We need T=1 for this to work, and IANA is allocating
ASM with T=0.

> Finally, it may make more sense to use ffxx:1000::/20 for ASM, and thus only use the rightmost bit of the four reserved bits (for RFC3956 at least)?

Yes, but it would mean that if in the future one wants to use a
new reserved bit for another purpose, then it won't work for
this purpose. I like the idea of using a single bit actually.

So here is an alternative proposal. Do you think it's better?

1. Update 3306 and give a new meaning to one of the remaining
    reserved bits.

2. Get a /96 for ASM from IANA (which would have T=0).

The first would allow for 3306 and 3956 addressing, which I
think is useful.

The second would allow for uses where people don't care for
that other type of addressing, and may also be useful if you
want to use more or less fixed addresses, that does not use
any particular unicast address.

The alternative of just getting a /96 for ASM from IANA is
in draft-kumar-mboned-64mcast-wkp-address-00.txt.

I guess just doing IANA assignments and reserving a bit
from 3306 are slightly separate problems, with different
issues and uses.

Finally, we also need a /96 for SSM. That can't just be
an IANA assignment either. One interesting thing here is
maybe that SSM is based on 3306 with plen and prefix set
to 0. So if a bit is reserved (from 3306), then I think
it would technically apply to SSM as well. But the SSM
implementations I've seen (as well as a couple of RFCs)
assume that these reserved bits are all 0. Not ignored
as they should have been...

Stig

> Tim
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>


From sarikaya2012@gmail.com  Fri Aug 17 12:21:01 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DEB421F85A0 for <mboned@ietfa.amsl.com>; Fri, 17 Aug 2012 12:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.563
X-Spam-Level: 
X-Spam-Status: No, score=-3.563 tagged_above=-999 required=5 tests=[AWL=0.036,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mOSWTeo7ccIP for <mboned@ietfa.amsl.com>; Fri, 17 Aug 2012 12:21:00 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 57BC621F8557 for <mboned@ietf.org>; Fri, 17 Aug 2012 12:21:00 -0700 (PDT)
Received: by iabz21 with SMTP id z21so1045520iab.31 for <mboned@ietf.org>; Fri, 17 Aug 2012 12:20:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ozsCmrLEx/o1KmlFnz45LEU0gE0knlPWbhccJa0Ypnw=; b=JJ1GiJZWlPb9T9ggqZttY4fM1434ayk6+MpNaIs3jPPhxLu2QDz1knO+oGvYuoDQFA yAEucmpBzR/SIpNB5e9MdRvIlaU9I+c4bnLy7VLhASmcK17DJICs7N/tgmra74gkKg8l gGnEhMEhRe9tI9OmrVbtM/0v+IAHDRZsy2kNKJgFnxy5cL2DKUJiPpE3IZRsV21Tae6H qjm6q5++OBrlYvqGgKr1A4kpYYhAAcNMtSqLyhUxPXjaRExBtuZZeM6jFOYJO4YF6KIc KCDInLrtJzBLuS96h/FzyxKx1snEcMC6F8/HSr4wgStMyB7kVRDr6jI7wDn6yfd1kADg 7pPQ==
MIME-Version: 1.0
Received: by 10.42.31.5 with SMTP id x5mr5254797icc.40.1345231259751; Fri, 17 Aug 2012 12:20:59 -0700 (PDT)
Received: by 10.231.55.70 with HTTP; Fri, 17 Aug 2012 12:20:59 -0700 (PDT)
In-Reply-To: <502E8819.5030901@venaas.com>
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com> <502AFECA.1090905@venaas.com> <2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <EMEW3|1c3fd9d33484c5343b2d7337b5211574o7G0Be03tjc|ecs.soton.ac.uk|2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <502E8819.5030901@venaas.com>
Date: Fri, 17 Aug 2012 14:20:59 -0500
Message-ID: <CAC8QAccRXZW=TUw3-6NSrOVy+t-iv9aqBGHzSP3tQw9_LD_S5g@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Stig Venaas <stig@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: mboned@ietf.org
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 19:21:01 -0000

On Fri, Aug 17, 2012 at 1:06 PM, Stig Venaas <stig@venaas.com> wrote:
> Hi Tim
>
>
> On 8/16/2012 4:12 PM, Tim Chown wrote:
>>
>> On 15 Aug 2012, at 02:43, Stig Venaas <stig@venaas.com> wrote:
>>
>>> On 14.08.2012 14:43, Lee, Yiu wrote:
>>>>
>>>> Hi Stig,
>>>>
>>>> Since we want T=1, this will not meet the "well-known" requirement
>>>> defined
>>>> in RFC4291. If we don't want to define a flag, what is the proper way to
>>>> describe ffxx:8000::/20 and ffxx:0:8000::/96?
>>>
>>>
>>> You could list them for all values of xx perhaps. I would maybe use
>>> "x" and "y" and then discuss the allowed values.
>>>
>>> There are scope relative allocations today, the main thing is that we
>>> don't want to require the flags to be "0". Or maybe we want to require
>>> the T-bit to be set. As I wrote earlier, I would think of these
>>> addresses as transient, and T=1 is required for Embedded-RP etc.
>>>
>>> The issue though is that if T=1, then it is not really an IANA
>>> allocation as I see it, because IANA allocations have T=0. But if there
>>> is IETF consensus, then one can still reserve these prefixes.
>>
>>
>> I agree with Stig; there are multiple prefixes being reserved here.
>>
>> The text is effectively updating both RFC3306 and RFC3956 since the above
>> prefix is setting a bit in the reserved bit range of both those
>> specifications.  RFC3306 also says all those reserved bits (17-24) must be
>> zero, while RFC3956 doesn't explicitly say that for bits 17-20 (it probably
>> should, if you're now using one of those bits).
>
>
> You're right about 3306. I wonder now if instead of practically
> reserving a specific value for the entire nibble of remaining
> reserved bits in 3306, it would be better to reserve just one of
> the bits. I don't think it updates 3956, because it doesn't talk
> about those bits at all, AFAICT.
>
>
>> Both RFCs say that if R or P flags are set, then T must be set too, so I'm
>> not sure you have freedom to say "if T=1" if you want to support those two
>> methods.
>
>
> Yes, that's why I've been saying that we can't just get an IANA
> allocation. We need T=1 for this to work, and IANA is allocating
> ASM with T=0.
>
>
>> Finally, it may make more sense to use ffxx:1000::/20 for ASM, and thus
>> only use the rightmost bit of the four reserved bits (for RFC3956 at least)?
>
>
> Yes, but it would mean that if in the future one wants to use a
> new reserved bit for another purpose, then it won't work for
> this purpose. I like the idea of using a single bit actually.
>
> So here is an alternative proposal. Do you think it's better?
>
> 1. Update 3306 and give a new meaning to one of the remaining
>    reserved bits.
>
> 2. Get a /96 for ASM from IANA (which would have T=0).
>
> The first would allow for 3306 and 3956 addressing, which I
> think is useful.
>
> The second would allow for uses where people don't care for
> that other type of addressing, and may also be useful if you
> want to use more or less fixed addresses, that does not use
> any particular unicast address.
>
> The alternative of just getting a /96 for ASM from IANA is
> in draft-kumar-mboned-64mcast-wkp-address-00.txt.
>
> I guess just doing IANA assignments and reserving a bit
> from 3306 are slightly separate problems, with different
> issues and uses.
>
> Finally, we also need a /96 for SSM. That can't just be
> an IANA assignment either. One interesting thing here is
> maybe that SSM is based on 3306 with plen and prefix set
> to 0. So if a bit is reserved (from 3306), then I think
> it would technically apply to SSM as well. But the SSM
> implementations I've seen (as well as a couple of RFCs)
> assume that these reserved bits are all 0. Not ignored
> as they should have been...


We just wanted to define two reserved multicast IPv6 prefixes and
after giving up modifying IP addressing architecture, we are now
talking about changing so many RFCs.

In this mail earlier Stig said:

http://www.ietf.org/mail-archive/web/mboned/current/msg01663.html

we can state that inter-domain operation is not a requirement and we
do not support embedded-RP.

Behcet

From stig@venaas.com  Fri Aug 17 12:50:38 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6256311E80E3 for <mboned@ietfa.amsl.com>; Fri, 17 Aug 2012 12:50:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.484
X-Spam-Level: 
X-Spam-Status: No, score=-102.484 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b0+Fs-csRh4e for <mboned@ietfa.amsl.com>; Fri, 17 Aug 2012 12:50:37 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id DD39C11E80E1 for <mboned@ietf.org>; Fri, 17 Aug 2012 12:50:36 -0700 (PDT)
Received: from [IPv6:2001:420:301:1004:3090:6830:dbf9:beb7] (unknown [IPv6:2001:420:301:1004:3090:6830:dbf9:beb7]) by ufisa.uninett.no (Postfix) with ESMTPSA id 0B6958003; Fri, 17 Aug 2012 21:50:34 +0200 (CEST)
Message-ID: <502EA087.2050803@venaas.com>
Date: Fri, 17 Aug 2012 12:50:31 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: sarikaya@ieee.org
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com> <502AFECA.1090905@venaas.com> <2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <EMEW3|1c3fd9d33484c5343b2d7337b5211574o7G0Be03tjc|ecs.soton.ac.uk|2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <502E8819.5030901@venaas.com> <CAC8QAccRXZW=TUw3-6NSrOVy+t-iv9aqBGHzSP3tQw9_LD_S5g@mail.gmail.com>
In-Reply-To: <CAC8QAccRXZW=TUw3-6NSrOVy+t-iv9aqBGHzSP3tQw9_LD_S5g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mboned@ietf.org, Behcet Sarikaya <sarikaya2012@gmail.com>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 19:50:38 -0000

On 8/17/2012 12:20 PM, Behcet Sarikaya wrote:
> On Fri, Aug 17, 2012 at 1:06 PM, Stig Venaas <stig@venaas.com> wrote:
>> Hi Tim
>>
>>
>> On 8/16/2012 4:12 PM, Tim Chown wrote:
>>>
>>> On 15 Aug 2012, at 02:43, Stig Venaas <stig@venaas.com> wrote:
>>>
>>>> On 14.08.2012 14:43, Lee, Yiu wrote:
>>>>>
>>>>> Hi Stig,
>>>>>
>>>>> Since we want T=1, this will not meet the "well-known" requirement
>>>>> defined
>>>>> in RFC4291. If we don't want to define a flag, what is the proper way to
>>>>> describe ffxx:8000::/20 and ffxx:0:8000::/96?
>>>>
>>>>
>>>> You could list them for all values of xx perhaps. I would maybe use
>>>> "x" and "y" and then discuss the allowed values.
>>>>
>>>> There are scope relative allocations today, the main thing is that we
>>>> don't want to require the flags to be "0". Or maybe we want to require
>>>> the T-bit to be set. As I wrote earlier, I would think of these
>>>> addresses as transient, and T=1 is required for Embedded-RP etc.
>>>>
>>>> The issue though is that if T=1, then it is not really an IANA
>>>> allocation as I see it, because IANA allocations have T=0. But if there
>>>> is IETF consensus, then one can still reserve these prefixes.
>>>
>>>
>>> I agree with Stig; there are multiple prefixes being reserved here.
>>>
>>> The text is effectively updating both RFC3306 and RFC3956 since the above
>>> prefix is setting a bit in the reserved bit range of both those
>>> specifications.  RFC3306 also says all those reserved bits (17-24) must be
>>> zero, while RFC3956 doesn't explicitly say that for bits 17-20 (it probably
>>> should, if you're now using one of those bits).
>>
>>
>> You're right about 3306. I wonder now if instead of practically
>> reserving a specific value for the entire nibble of remaining
>> reserved bits in 3306, it would be better to reserve just one of
>> the bits. I don't think it updates 3956, because it doesn't talk
>> about those bits at all, AFAICT.
>>
>>
>>> Both RFCs say that if R or P flags are set, then T must be set too, so I'm
>>> not sure you have freedom to say "if T=1" if you want to support those two
>>> methods.
>>
>>
>> Yes, that's why I've been saying that we can't just get an IANA
>> allocation. We need T=1 for this to work, and IANA is allocating
>> ASM with T=0.
>>
>>
>>> Finally, it may make more sense to use ffxx:1000::/20 for ASM, and thus
>>> only use the rightmost bit of the four reserved bits (for RFC3956 at least)?
>>
>>
>> Yes, but it would mean that if in the future one wants to use a
>> new reserved bit for another purpose, then it won't work for
>> this purpose. I like the idea of using a single bit actually.
>>
>> So here is an alternative proposal. Do you think it's better?
>>
>> 1. Update 3306 and give a new meaning to one of the remaining
>>     reserved bits.
>>
>> 2. Get a /96 for ASM from IANA (which would have T=0).
>>
>> The first would allow for 3306 and 3956 addressing, which I
>> think is useful.
>>
>> The second would allow for uses where people don't care for
>> that other type of addressing, and may also be useful if you
>> want to use more or less fixed addresses, that does not use
>> any particular unicast address.
>>
>> The alternative of just getting a /96 for ASM from IANA is
>> in draft-kumar-mboned-64mcast-wkp-address-00.txt.
>>
>> I guess just doing IANA assignments and reserving a bit
>> from 3306 are slightly separate problems, with different
>> issues and uses.
>>
>> Finally, we also need a /96 for SSM. That can't just be
>> an IANA assignment either. One interesting thing here is
>> maybe that SSM is based on 3306 with plen and prefix set
>> to 0. So if a bit is reserved (from 3306), then I think
>> it would technically apply to SSM as well. But the SSM
>> implementations I've seen (as well as a couple of RFCs)
>> assume that these reserved bits are all 0. Not ignored
>> as they should have been...
>
>
> We just wanted to define two reserved multicast IPv6 prefixes and
> after giving up modifying IP addressing architecture, we are now
> talking about changing so many RFCs.
>
> In this mail earlier Stig said:
>
> http://www.ietf.org/mail-archive/web/mboned/current/msg01663.html
>
> we can state that inter-domain operation is not a requirement and we
> do not support embedded-RP.

I wrote something slightly different:

"Of course we could argue whether we need to support embedded-RP.
It is very useful, especially inter-domain, but if that is not a
requirement, we may not need to support it."

I left it open to discussion. I'm trying to get all the options on the
table here.

Alternative 2 above is sufficient if we don't care about embedded-RP,
and is in draft-kumar-mboned-64mcast-wkp-address-00.txt.

But I do see value in both unicast-prefix based addressing (a good
way to ensure your addresses are unique), and embedded-RP (which is
necessary inter-domain, but may at times be used intra-domain). And I
do know deployments using inter-domain embedded-RP.

If we want to support unicast-prefix based addressing or
embedded-RP, it appears we need to update RFC 3306.

Note that we would not change 3306 in any way. We only need
this draft to say that it Updates 3306.

Stig

>
> Behcet
>


From peter@denic.de  Sun Aug 19 22:35:20 2012
Return-Path: <peter@denic.de>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA7C621F8565 for <mboned@ietfa.amsl.com>; Sun, 19 Aug 2012 22:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o-r2MEBX764T for <mboned@ietfa.amsl.com>; Sun, 19 Aug 2012 22:35:19 -0700 (PDT)
Received: from office.denic.de (office.denic.de [IPv6:2a02:568:122:16:1::3]) by ietfa.amsl.com (Postfix) with ESMTP id 3729C21F861F for <mboned@ietf.org>; Sun, 19 Aug 2012 22:35:18 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.17]) by office.denic.de with esmtp   id 1T3Kdw-0001X2-A8; Mon, 20 Aug 2012 07:35:16 +0200
Received: from localhost by x27.adm.denic.de with local  id 1T3Kdw-00058k-6c; Mon, 20 Aug 2012 07:35:16 +0200
Date: Mon, 20 Aug 2012 07:35:16 +0200
From: Peter Koch <pk@DENIC.DE>
To: mboned@ietf.org
Message-ID: <20120820053516.GT19035@x28.adm.denic.de>
Mail-Followup-To: mboned@ietf.org
References: <20120810064908.22316.70512.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120810064908.22316.70512.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Aug 2012 05:35:20 -0000

> 	Filename        : draft-ietf-mboned-64-multicast-address-format-03.txt

> 3.1.  Reserving Dedicated Prefixes
>    3:  Avoid ff3x::4000:0001-ff3x::7fff:ffff which is reserved for IANA.

Is "for IANA" really meant here?  If so, what is IANA going to do with this space?

> 5.  IANA Considerations
>    Authors of this document request to reserve:

Wording: "This document asks/requests IANA to reserve ..."

-Peter

From mohamed.boucadair@orange.com  Sun Aug 19 22:42:42 2012
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A409F21F84AF for <mboned@ietfa.amsl.com>; Sun, 19 Aug 2012 22:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.03
X-Spam-Level: 
X-Spam-Status: No, score=-2.03 tagged_above=-999 required=5 tests=[AWL=0.218,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IktkgowHh0fQ for <mboned@ietfa.amsl.com>; Sun, 19 Aug 2012 22:42:42 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 0D1C421F84A2 for <mboned@ietf.org>; Sun, 19 Aug 2012 22:42:41 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id A0FA8324AF1; Mon, 20 Aug 2012 07:42:40 +0200 (CEST)
Received: from PUEXCH51.nanterre.francetelecom.fr (unknown [10.101.44.31]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 869E627C053; Mon, 20 Aug 2012 07:42:40 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH51.nanterre.francetelecom.fr ([10.101.44.31]) with mapi; Mon, 20 Aug 2012 07:42:21 +0200
From: <mohamed.boucadair@orange.com>
To: Peter Koch <pk@DENIC.DE>, "mboned@ietf.org" <mboned@ietf.org>
Date: Mon, 20 Aug 2012 07:42:19 +0200
Thread-Topic: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
Thread-Index: Ac1+lZCC3n+qKC7SS5yqL7Cv2wdd6AAAFJ/g
Message-ID: <94C682931C08B048B7A8645303FDC9F36E512B4520@PUEXCB1B.nanterre.francetelecom.fr>
References: <20120810064908.22316.70512.idtracker@ietfa.amsl.com> <20120820053516.GT19035@x28.adm.denic.de>
In-Reply-To: <20120820053516.GT19035@x28.adm.denic.de>
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: 2012.8.20.42417
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Aug 2012 05:42:42 -0000

Dear Peter,

Please see inline.

Cheers,
Med=20

>-----Message d'origine-----
>De : mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org]=20
>De la part de Peter Koch
>Envoy=E9 : lundi 20 ao=FBt 2012 07:35
>=C0 : mboned@ietf.org
>Objet : Re: [MBONED]=20
>draft-ietf-mboned-64-multicast-address-format-03.txt
>
>> 	Filename        :=20
>draft-ietf-mboned-64-multicast-address-format-03.txt
>
>> 3.1.  Reserving Dedicated Prefixes
>>    3:  Avoid ff3x::4000:0001-ff3x::7fff:ffff which is=20
>reserved for IANA.
>
>Is "for IANA" really meant here?  If so, what is IANA going to=20
>do with this space?

Med: We meant it is reserved for IANA allocation. Will clarify the text.


>
>> 5.  IANA Considerations
>>    Authors of this document request to reserve:
>
>Wording: "This document asks/requests IANA to reserve ..."

Med: Updated in my local copy. Thanks.

>
>-Peter
>_______________________________________________
>MBONED mailing list
>MBONED@ietf.org
>https://www.ietf.org/mailman/listinfo/mboned
>=

From mohamed.boucadair@orange.com  Sun Aug 19 22:58:51 2012
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D78621F8646 for <mboned@ietfa.amsl.com>; Sun, 19 Aug 2012 22:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.033
X-Spam-Level: 
X-Spam-Status: No, score=-2.033 tagged_above=-999 required=5 tests=[AWL=0.215,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BG9a1LMMU-TU for <mboned@ietfa.amsl.com>; Sun, 19 Aug 2012 22:58:51 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id B5BEC21F8643 for <mboned@ietf.org>; Sun, 19 Aug 2012 22:58:50 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id A5A492647D2; Mon, 20 Aug 2012 07:58:49 +0200 (CEST)
Received: from PUEXCH61.nanterre.francetelecom.fr (unknown [10.101.44.32]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 8835835C048; Mon, 20 Aug 2012 07:58:49 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH61.nanterre.francetelecom.fr ([10.101.44.32]) with mapi; Mon, 20 Aug 2012 07:58:29 +0200
From: <mohamed.boucadair@orange.com>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>, Stig Venaas <stig@venaas.com>
Date: Mon, 20 Aug 2012 07:58:29 +0200
Thread-Topic: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
Thread-Index: Ac18rWuy/+BxsNfYSk+GxR5/giu0uwB6d3lg
Message-ID: <94C682931C08B048B7A8645303FDC9F36E512B4526@PUEXCB1B.nanterre.francetelecom.fr>
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com> <502AFECA.1090905@venaas.com> <2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <EMEW3|1c3fd9d33484c5343b2d7337b5211574o7G0Be03tjc|ecs.soton.ac.uk|2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <502E8819.5030901@venaas.com> <CAC8QAccRXZW=TUw3-6NSrOVy+t-iv9aqBGHzSP3tQw9_LD_S5g@mail.gmail.com>
In-Reply-To: <CAC8QAccRXZW=TUw3-6NSrOVy+t-iv9aqBGHzSP3tQw9_LD_S5g@mail.gmail.com>
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: 2012.8.20.50040
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Aug 2012 05:58:51 -0000

Hi Behcet,

There is a real value to ensure compatibility with unicast based and embedd=
ed-RP for ASM. As pointed by T. Chown this would require to update rfc3306 =
but I don't think this is problematic.

Now for Stig's Idea to reserve an additional /96 prefix (for ASM, T=3D0), w=
e need more feedback from the WG.

Cheers,
Med
=20

>-----Message d'origine-----
>De : mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org]=20
>De la part de Behcet Sarikaya
>Envoy=E9 : vendredi 17 ao=FBt 2012 21:21
>=C0 : Stig Venaas
>Cc : mboned@ietf.org
>Objet : Re: [MBONED]=20
>draft-ietf-mboned-64-multicast-address-format-03.txt
>
>On Fri, Aug 17, 2012 at 1:06 PM, Stig Venaas <stig@venaas.com> wrote:
>> Hi Tim
>>
>>
>> On 8/16/2012 4:12 PM, Tim Chown wrote:
>>>
>>> On 15 Aug 2012, at 02:43, Stig Venaas <stig@venaas.com> wrote:
>>>
>>>> On 14.08.2012 14:43, Lee, Yiu wrote:
>>>>>
>>>>> Hi Stig,
>>>>>
>>>>> Since we want T=3D1, this will not meet the "well-known" requirement
>>>>> defined
>>>>> in RFC4291. If we don't want to define a flag, what is=20
>the proper way to
>>>>> describe ffxx:8000::/20 and ffxx:0:8000::/96?
>>>>
>>>>
>>>> You could list them for all values of xx perhaps. I would maybe use
>>>> "x" and "y" and then discuss the allowed values.
>>>>
>>>> There are scope relative allocations today, the main thing=20
>is that we
>>>> don't want to require the flags to be "0". Or maybe we=20
>want to require
>>>> the T-bit to be set. As I wrote earlier, I would think of these
>>>> addresses as transient, and T=3D1 is required for Embedded-RP etc.
>>>>
>>>> The issue though is that if T=3D1, then it is not really an IANA
>>>> allocation as I see it, because IANA allocations have T=3D0.=20
>But if there
>>>> is IETF consensus, then one can still reserve these prefixes.
>>>
>>>
>>> I agree with Stig; there are multiple prefixes being reserved here.
>>>
>>> The text is effectively updating both RFC3306 and RFC3956=20
>since the above
>>> prefix is setting a bit in the reserved bit range of both those
>>> specifications.  RFC3306 also says all those reserved bits=20
>(17-24) must be
>>> zero, while RFC3956 doesn't explicitly say that for bits=20
>17-20 (it probably
>>> should, if you're now using one of those bits).
>>
>>
>> You're right about 3306. I wonder now if instead of practically
>> reserving a specific value for the entire nibble of remaining
>> reserved bits in 3306, it would be better to reserve just one of
>> the bits. I don't think it updates 3956, because it doesn't talk
>> about those bits at all, AFAICT.
>>
>>
>>> Both RFCs say that if R or P flags are set, then T must be=20
>set too, so I'm
>>> not sure you have freedom to say "if T=3D1" if you want to=20
>support those two
>>> methods.
>>
>>
>> Yes, that's why I've been saying that we can't just get an IANA
>> allocation. We need T=3D1 for this to work, and IANA is allocating
>> ASM with T=3D0.
>>
>>
>>> Finally, it may make more sense to use ffxx:1000::/20 for=20
>ASM, and thus
>>> only use the rightmost bit of the four reserved bits (for=20
>RFC3956 at least)?
>>
>>
>> Yes, but it would mean that if in the future one wants to use a
>> new reserved bit for another purpose, then it won't work for
>> this purpose. I like the idea of using a single bit actually.
>>
>> So here is an alternative proposal. Do you think it's better?
>>
>> 1. Update 3306 and give a new meaning to one of the remaining
>>    reserved bits.
>>
>> 2. Get a /96 for ASM from IANA (which would have T=3D0).
>>
>> The first would allow for 3306 and 3956 addressing, which I
>> think is useful.
>>
>> The second would allow for uses where people don't care for
>> that other type of addressing, and may also be useful if you
>> want to use more or less fixed addresses, that does not use
>> any particular unicast address.
>>
>> The alternative of just getting a /96 for ASM from IANA is
>> in draft-kumar-mboned-64mcast-wkp-address-00.txt.
>>
>> I guess just doing IANA assignments and reserving a bit
>> from 3306 are slightly separate problems, with different
>> issues and uses.
>>
>> Finally, we also need a /96 for SSM. That can't just be
>> an IANA assignment either. One interesting thing here is
>> maybe that SSM is based on 3306 with plen and prefix set
>> to 0. So if a bit is reserved (from 3306), then I think
>> it would technically apply to SSM as well. But the SSM
>> implementations I've seen (as well as a couple of RFCs)
>> assume that these reserved bits are all 0. Not ignored
>> as they should have been...
>
>
>We just wanted to define two reserved multicast IPv6 prefixes and
>after giving up modifying IP addressing architecture, we are now
>talking about changing so many RFCs.
>
>In this mail earlier Stig said:
>
>http://www.ietf.org/mail-archive/web/mboned/current/msg01663.html
>
>we can state that inter-domain operation is not a requirement and we
>do not support embedded-RP.
>
>Behcet
>_______________________________________________
>MBONED mailing list
>MBONED@ietf.org
>https://www.ietf.org/mailman/listinfo/mboned
>=

From jacni@jacni.com  Mon Aug 20 02:29:24 2012
Return-Path: <jacni@jacni.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE7021F86E3 for <mboned@ietfa.amsl.com>; Mon, 20 Aug 2012 02:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.52
X-Spam-Level: 
X-Spam-Status: No, score=-2.52 tagged_above=-999 required=5 tests=[AWL=1.078,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j+RNv4ZBY9kf for <mboned@ietfa.amsl.com>; Mon, 20 Aug 2012 02:29:23 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 328EB21F86D9 for <mboned@ietf.org>; Mon, 20 Aug 2012 02:29:23 -0700 (PDT)
Received: by dakr19 with SMTP id r19so2211010dak.31 for <mboned@ietf.org>; Mon, 20 Aug 2012 02:29:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:x-gm-message-state; bh=6pQPmGmRzLW7/S7k0nOe7ZU+AVzG++PYkdAo9t+CDHM=; b=LbrHoJczMhcJZermRuwsEZrQj0UmgmphUz6ACHzJ7E73oyNw/n1a3n8RtONR//jwM8 NoT39qU1ZQXK91DIsjy/iMvfEmM11hjfDhnSjYP0t77oFloiDxsHse6X666sRjfpxoQk t2s/HaZhTcwG3dWulIfrkkqcfmgCvU16OtgSJ51WARxTGV//+LToUjJeTo8clJxRasYe OVqkKOD9BlFdMJW45pohTzVIxO6TfJIx3iUus8VuGj/v8UKPvornV+fntMqYyau2w/vc VVbBZTlwcAhvgPfvIZRLIFPf2G/c1GwmLWCV+iZGvaMZ3I0s2mZnJF/KOudwPiELIMHJ 9SjA==
Received: by 10.66.75.133 with SMTP id c5mr28610309paw.24.1345454962599; Mon, 20 Aug 2012 02:29:22 -0700 (PDT)
Received: from [10.75.234.114] (64-104-125-217.cisco.com. [64.104.125.217]) by mx.google.com with ESMTPS id jz4sm10761384pbc.17.2012.08.20.02.29.20 (version=SSLv3 cipher=OTHER); Mon, 20 Aug 2012 02:29:21 -0700 (PDT)
Message-ID: <5032036E.3050006@jacni.com>
Date: Mon, 20 Aug 2012 17:29:18 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Stig Venaas <stig@venaas.com>
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com> <502AFECA.1090905@venaas.com> <2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <EMEW3|1c3fd9d33484c5343b2d7337b5211574o7G0Be03tjc|ecs.soton.ac.uk|2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <502E8819.5030901@venaas.com>
In-Reply-To: <502E8819.5030901@venaas.com>
Content-Type: multipart/alternative; boundary="------------000507060104060305030207"
X-Gm-Message-State: ALoCoQmwjv12iyEk4foIYkhv0isKwLjFejho3pMdIM53HbYfkNcxqAXLaQeWR+Nj9QkAfBUWQyU1
Cc: mboned@ietf.org
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Aug 2012 09:29:24 -0000

This is a multi-part message in MIME format.
--------------000507060104060305030207
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

hi,

On 8/18/2012 Saturday 2:06 AM, Stig Venaas wrote:
> Hi Tim
>
> On 8/16/2012 4:12 PM, Tim Chown wrote:
>> On 15 Aug 2012, at 02:43, Stig Venaas <stig@venaas.com> wrote:
>>
>>> On 14.08.2012 14:43, Lee, Yiu wrote:
>>>> Hi Stig,
>>>>
>>>> Since we want T=1, this will not meet the "well-known" requirement
>>>> defined
>>>> in RFC4291. If we don't want to define a flag, what is the proper
>>>> way to
>>>> describe ffxx:8000::/20 and ffxx:0:8000::/96?
>>>
>>> You could list them for all values of xx perhaps. I would maybe use
>>> "x" and "y" and then discuss the allowed values.
>>>
>>> There are scope relative allocations today, the main thing is that we
>>> don't want to require the flags to be "0". Or maybe we want to require
>>> the T-bit to be set. As I wrote earlier, I would think of these
>>> addresses as transient, and T=1 is required for Embedded-RP etc.
>>>
>>> The issue though is that if T=1, then it is not really an IANA
>>> allocation as I see it, because IANA allocations have T=0. But if there
>>> is IETF consensus, then one can still reserve these prefixes.
>>
>> I agree with Stig; there are multiple prefixes being reserved here.
>>
>> The text is effectively updating both RFC3306 and RFC3956 since the
>> above prefix is setting a bit in the reserved bit range of both those
>> specifications. RFC3306 also says all those reserved bits (17-24)
>> must be zero, while RFC3956 doesn't explicitly say that for bits
>> 17-20 (it probably should, if you're now using one of those bits).
>
> You're right about 3306. I wonder now if instead of practically
> reserving a specific value for the entire nibble of remaining
> reserved bits in 3306, it would be better to reserve just one of
> the bits. I don't think it updates 3956, because it doesn't talk
> about those bits at all, AFAICT.
>
>> Both RFCs say that if R or P flags are set, then T must be set too,
>> so I'm not sure you have freedom to say "if T=1" if you want to
>> support those two methods.
>
> Yes, that's why I've been saying that we can't just get an IANA
> allocation. We need T=1 for this to work, and IANA is allocating
> ASM with T=0.
>
>> Finally, it may make more sense to use ffxx:1000::/20 for ASM, and
>> thus only use the rightmost bit of the four reserved bits (for
>> RFC3956 at least)?
>
> Yes, but it would mean that if in the future one wants to use a
> new reserved bit for another purpose, then it won't work for
> this purpose. I like the idea of using a single bit actually.
>
> So here is an alternative proposal. Do you think it's better?
>
> 1. Update 3306 and give a new meaning to one of the remaining
> reserved bits.

Sounds good, and it works for SSM, ASM with unicast-based prefix feature
and ASM with embedded-rp feature.

>
> 2. Get a /96 for ASM from IANA (which would have T=0).
>
> The first would allow for 3306 and 3956 addressing, which I
> think is useful.
>
> The second would allow for uses where people don't care for
> that other type of addressing, and may also be useful if you
> want to use more or less fixed addresses, that does not use
> any particular unicast address.
>
> The alternative of just getting a /96 for ASM from IANA is
> in draft-kumar-mboned-64mcast-wkp-address-00.txt.
>
> I guess just doing IANA assignments and reserving a bit
> from 3306 are slightly separate problems, with different
> issues and uses.
>
> Finally, we also need a /96 for SSM. That can't just be
> an IANA assignment either. One interesting thing here is
> maybe that SSM is based on 3306 with plen and prefix set
> to 0. So if a bit is reserved (from 3306), then I think
> it would technically apply to SSM as well. 
Sorry, I'm a little confused here. If 1 bit approach works, why do we
need a /96 for SSM? Did I miss anything?


Cheers,
Jacni

> But the SSM
> implementations I've seen (as well as a couple of RFCs)
> assume that these reserved bits are all 0. Not ignored
> as they should have been...
>
> Stig
>
>> Tim
>> _______________________________________________
>> MBONED mailing list
>> MBONED@ietf.org
>> https://www.ietf.org/mailman/listinfo/mboned
>>
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
> .
>


--------------000507060104060305030207
Content-Type: text/html; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-2022-JP"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,<br>
      <br>
    </font>
    <div class="moz-cite-prefix">On 8/18/2012 Saturday 2:06 AM, Stig
      Venaas wrote:<br>
    </div>
    <blockquote cite="mid:502E8819.5030901@venaas.com" type="cite">Hi
      Tim
      <br>
      <br>
      On 8/16/2012 4:12 PM, Tim Chown wrote:
      <br>
      <blockquote type="cite">On 15 Aug 2012, at 02:43, Stig Venaas
        <a class="moz-txt-link-rfc2396E" href="mailto:stig@venaas.com">&lt;stig@venaas.com&gt;</a> wrote:
        <br>
        <br>
        <blockquote type="cite">On 14.08.2012 14:43, Lee, Yiu wrote:
          <br>
          <blockquote type="cite">Hi Stig,
            <br>
            <br>
            Since we want T=1, this will not meet the "well-known"
            requirement defined
            <br>
            in RFC4291. If we don't want to define a flag, what is the
            proper way to
            <br>
            describe ffxx:8000::/20 and ffxx:0:8000::/96?
            <br>
          </blockquote>
          <br>
          You could list them for all values of xx perhaps. I would
          maybe use
          <br>
          "x" and "y" and then discuss the allowed values.
          <br>
          <br>
          There are scope relative allocations today, the main thing is
          that we
          <br>
          don't want to require the flags to be "0". Or maybe we want to
          require
          <br>
          the T-bit to be set. As I wrote earlier, I would think of
          these
          <br>
          addresses as transient, and T=1 is required for Embedded-RP
          etc.
          <br>
          <br>
          The issue though is that if T=1, then it is not really an IANA
          <br>
          allocation as I see it, because IANA allocations have T=0. But
          if there
          <br>
          is IETF consensus, then one can still reserve these prefixes.
          <br>
        </blockquote>
        <br>
        I agree with Stig; there are multiple prefixes being reserved
        here.
        <br>
        <br>
        The text is effectively updating both RFC3306 and RFC3956 since
        the above prefix is setting a bit in the reserved bit range of
        both those specifications.&nbsp; RFC3306 also says all those reserved
        bits (17-24) must be zero, while RFC3956 doesn't explicitly say
        that for bits 17-20 (it probably should, if you're now using one
        of those bits).
        <br>
      </blockquote>
      <br>
      You're right about 3306. I wonder now if instead of practically
      <br>
      reserving a specific value for the entire nibble of remaining
      <br>
      reserved bits in 3306, it would be better to reserve just one of
      <br>
      the bits. I don't think it updates 3956, because it doesn't talk
      <br>
      about those bits at all, AFAICT.
      <br>
      <br>
      <blockquote type="cite">Both RFCs say that if R or P flags are
        set, then T must be set too, so I'm not sure you have freedom to
        say "if T=1" if you want to support those two methods.
        <br>
      </blockquote>
      <br>
      Yes, that's why I've been saying that we can't just get an IANA
      <br>
      allocation. We need T=1 for this to work, and IANA is allocating
      <br>
      ASM with T=0.
      <br>
      <br>
      <blockquote type="cite">Finally, it may make more sense to use
        ffxx:1000::/20 for ASM, and thus only use the rightmost bit of
        the four reserved bits (for RFC3956 at least)?
        <br>
      </blockquote>
      <br>
      Yes, but it would mean that if in the future one wants to use a
      <br>
      new reserved bit for another purpose, then it won't work for
      <br>
      this purpose. I like the idea of using a single bit actually.
      <br>
      <br>
      So here is an alternative proposal. Do you think it's better?
      <br>
      <br>
      1. Update 3306 and give a new meaning to one of the remaining
      <br>
      &nbsp;&nbsp; reserved bits.
      <br>
    </blockquote>
    <br>
    <font face="Calibri">Sounds good, and it works for SSM, ASM with
      unicast-based prefix feature and ASM with embedded-rp feature.<br>
    </font><br>
    <blockquote cite="mid:502E8819.5030901@venaas.com" type="cite">
      <br>
      2. Get a /96 for ASM from IANA (which would have T=0).
      <br>
      <br>
      The first would allow for 3306 and 3956 addressing, which I
      <br>
      think is useful.
      <br>
      <br>
      The second would allow for uses where people don't care for
      <br>
      that other type of addressing, and may also be useful if you
      <br>
      want to use more or less fixed addresses, that does not use
      <br>
      any particular unicast address.
      <br>
      <br>
      The alternative of just getting a /96 for ASM from IANA is
      <br>
      in draft-kumar-mboned-64mcast-wkp-address-00.txt.
      <br>
      <br>
      I guess just doing IANA assignments and reserving a bit
      <br>
      from 3306 are slightly separate problems, with different
      <br>
      issues and uses.
      <br>
      <br>
      Finally, we also need a /96 for SSM. That can't just be
      <br>
      an IANA assignment either. One interesting thing here is
      <br>
      maybe that SSM is based on 3306 with plen and prefix set
      <br>
      to 0. So if a bit is reserved (from 3306), then I think
      <br>
      it would technically apply to SSM as well. </blockquote>
    <font face="Calibri">Sorry, I'm a little confused here. If 1 bit
      approach works, why do we need a /96 for SSM? Did I miss anything?<br>
      <br>
      <br>
      Cheers,<br>
      Jacni<br>
      <br>
    </font>
    <blockquote cite="mid:502E8819.5030901@venaas.com" type="cite">But
      the SSM
      <br>
      implementations I've seen (as well as a couple of RFCs)
      <br>
      assume that these reserved bits are all 0. Not ignored
      <br>
      as they should have been...
      <br>
      <br>
      Stig
      <br>
      <br>
      <blockquote type="cite">Tim
        <br>
        _______________________________________________
        <br>
        MBONED mailing list
        <br>
        <a class="moz-txt-link-abbreviated" href="mailto:MBONED@ietf.org">MBONED@ietf.org</a>
        <br>
        <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mboned">https://www.ietf.org/mailman/listinfo/mboned</a>
        <br>
        <br>
      </blockquote>
      <br>
      _______________________________________________
      <br>
      MBONED mailing list
      <br>
      <a class="moz-txt-link-abbreviated" href="mailto:MBONED@ietf.org">MBONED@ietf.org</a>
      <br>
      <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mboned">https://www.ietf.org/mailman/listinfo/mboned</a>
      <br>
      .
      <br>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------000507060104060305030207--

From sarikaya2012@gmail.com  Mon Aug 20 12:49:43 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6D8221F8629 for <mboned@ietfa.amsl.com>; Mon, 20 Aug 2012 12:49:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.263
X-Spam-Level: 
X-Spam-Status: No, score=-3.263 tagged_above=-999 required=5 tests=[AWL=-0.264, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DUH2YgeNPpzE for <mboned@ietfa.amsl.com>; Mon, 20 Aug 2012 12:49:43 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3E56521F861A for <mboned@ietf.org>; Mon, 20 Aug 2012 12:49:43 -0700 (PDT)
Received: by yhq56 with SMTP id 56so5911251yhq.31 for <mboned@ietf.org>; Mon, 20 Aug 2012 12:49:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Eh/JxsrN94V3rOe5+E5sk7IplZIcvfrnXM5PVsZzeyM=; b=nYaft6qBo8pHCmgbgbxcBX75mjAobpEO/3Ny1ehXeZR7ZmblSd0ZtccVm8Rruq5QuO dwEpFm1NAkhuVPNRFFx+bBMd3Ix4rEQ+3Es43+FtQhhNA6v4U+dpIFrsuNIYdjJ1NANG kPILFgpvuOuKRPH72HwOVSwp6jmRHnbxdj68e0D5sxkA7Cn/3BAmAaJz7FC4wlfFPv6e iOT9y+u72KYb/RGvfM4iMretfbtRDw0Dh370fzeK4ETTcCyGvIGfD1/5Dguvbk3EsKED gi4WN8hTWswrBd0eGz2sqlrYhFaHw0b0TK1PC+VeMoWTpkVUJA8KmTGoYMBRWkM2nKOK W4Qw==
MIME-Version: 1.0
Received: by 10.50.159.226 with SMTP id xf2mr10765261igb.41.1345492182297; Mon, 20 Aug 2012 12:49:42 -0700 (PDT)
Received: by 10.231.55.70 with HTTP; Mon, 20 Aug 2012 12:49:42 -0700 (PDT)
In-Reply-To: <502EA087.2050803@venaas.com>
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com> <502AFECA.1090905@venaas.com> <2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <EMEW3|1c3fd9d33484c5343b2d7337b5211574o7G0Be03tjc|ecs.soton.ac.uk|2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <502E8819.5030901@venaas.com> <CAC8QAccRXZW=TUw3-6NSrOVy+t-iv9aqBGHzSP3tQw9_LD_S5g@mail.gmail.com> <502EA087.2050803@venaas.com>
Date: Mon, 20 Aug 2012 14:49:42 -0500
Message-ID: <CAC8QAccswaS3cTqAdoEUzb4hnFO+qd=cx71k5mdsbo5GJNx6LA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Stig Venaas <stig@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: mboned@ietf.org
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Aug 2012 19:49:43 -0000

> I wrote something slightly different:
>
> "Of course we could argue whether we need to support embedded-RP.
> It is very useful, especially inter-domain, but if that is not a
> requirement, we may not need to support it."
>

Embedded-RP prefix is FF7e, so FFxx supports it.

> I left it open to discussion. I'm trying to get all the options on the
> table here.
>
> Alternative 2 above is sufficient if we don't care about embedded-RP,
> and is in draft-kumar-mboned-64mcast-wkp-address-00.txt.
>
> But I do see value in both unicast-prefix based addressing (a good
> way to ensure your addresses are unique), and embedded-RP (which is
> necessary inter-domain, but may at times be used intra-domain). And I
> do know deployments using inter-domain embedded-RP.
>
> If we want to support unicast-prefix based addressing or
> embedded-RP, it appears we need to update RFC 3306.
>
> Note that we would not change 3306 in any way. We only need
> this draft to say that it Updates 3306.

Why?
As far as I understand, the issue here is to use which bit in the
reserved field, Tim suggested the rightmost and your proposal uses the
leftmost.
RFC3946 solves this problem by redefining rsvd field as 4 bits instead
of 8 bits in RFC 3306, i.e. it updates 3306 which is already stated in
there.

Maybe in this draft we can say that we use RFC 3946 definition of the
reserved field.

BTW, in Teemu Kiviniemi's thesis on Implementation of an IPv4 to IPv6 Multicast
Translator
ASM prefix: ff7e:140:2001:db8:ab:cd::/96
is used, which matches Tim's suggestion :-).

This is the SSM prefix: ff3e::/96 that is used.


Behcet

From tjc@ecs.soton.ac.uk  Mon Aug 20 15:40:08 2012
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31B4B21F851C for <mboned@ietfa.amsl.com>; Mon, 20 Aug 2012 15:40:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.271
X-Spam-Level: 
X-Spam-Status: No, score=-1.271 tagged_above=-999 required=5 tests=[AWL=-0.668, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id blUZJGBmODYD for <mboned@ietfa.amsl.com>; Mon, 20 Aug 2012 15:40:07 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 40C7D21F8513 for <mboned@ietf.org>; Mon, 20 Aug 2012 15:39:53 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q7KMdlt0016342; Mon, 20 Aug 2012 23:39:47 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk q7KMdlt0016342
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1345502388; bh=0wJVPv7VcHke4DGurFrmAVRrY+4=; h=References:In-Reply-To:Mime-Version:Cc:From:Subject:Date:To; b=yNb/n8Ww7WScWsFe7nEIuGMadY6x8t5qNXoaY3J5Qyvfo4bK5p3IEotCKJkocEUMb mQkArBabUsX97Zd/XWOaA3JrfkQSWzW0cihHECu3yi+vsD7TTirBxQyjoPp7R8W7qe JfbxMmBz5Uh8Tbn3KqGShfe2hg3qR9dSnsav0E0w=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id o7JNdl0430621303NH ret-id none; Mon, 20 Aug 2012 23:39:48 +0100
Received: from [192.168.1.101] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q7KMcR95009694 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 20 Aug 2012 23:38:28 +0100
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com> <502AFECA.1090905@venaas.com> <2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <EMEW3|1c3fd9d33484c5343b2d7337b5211574o7G0Be03tjc|ecs.soton.ac.uk|2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <502E8819.5030901@venaas.com> <CAC8QAccRXZW=TUw3-6NSrOVy+t-iv9aqBGHzSP3tQw9_LD_S5g@mail.gmail.com> <502EA087.2050803@venaas.com> <CAC8QAccswaS3cTqAdoEUzb4hnFO+qd=cx71k5mdsbo5GJNx6LA@mail.gmail.com> <E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk>
In-Reply-To: <CAC8QAccswaS3cTqAdoEUzb4hnFO+qd=cx71k5mdsbo5GJNx6LA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-ID: <EMEW3|b1f060ff67b81d8a57bf37f9620b398co7JNdl03tjc|ecs.soton.ac.uk|E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk>
X-Mailer: iPad Mail (9B206)
From: Tim Chown <tjc@ecs.soton.ac.uk>
Date: Mon, 20 Aug 2012 23:39:00 +0100
To: "sarikaya@ieee.org" <sarikaya@ieee.org>
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=o7JNdl043062130300; tid=o7JNdl0430621303NH; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: q7KMdlt0016342
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Aug 2012 22:40:08 -0000

On 20 Aug 2012, at 20:49, Behcet Sarikaya <sarikaya2012@gmail.com> wrote:

>> I wrote something slightly different:
>>=20
>> "Of course we could argue whether we need to support embedded-RP.
>> It is very useful, especially inter-domain, but if that is not a
>> requirement, we may not need to support it."
>>=20
>=20
> Embedded-RP prefix is FF7e, so FFxx supports it.

Well, it uses ff7x.  We use embedded RP intra-domain on our campus, not just=
 inter-domain.

>> I left it open to discussion. I'm trying to get all the options on the
>> table here.
>>=20
>> Alternative 2 above is sufficient if we don't care about embedded-RP,
>> and is in draft-kumar-mboned-64mcast-wkp-address-00.txt.
>>=20
>> But I do see value in both unicast-prefix based addressing (a good
>> way to ensure your addresses are unique), and embedded-RP (which is
>> necessary inter-domain, but may at times be used intra-domain). And I
>> do know deployments using inter-domain embedded-RP.
>>=20
>> If we want to support unicast-prefix based addressing or
>> embedded-RP, it appears we need to update RFC 3306.
>>=20
>> Note that we would not change 3306 in any way. We only need
>> this draft to say that it Updates 3306.
>=20
> Why?
> As far as I understand, the issue here is to use which bit in the
> reserved field, Tim suggested the rightmost and your proposal uses the
> leftmost.
> RFC3946 solves this problem by redefining rsvd field as 4 bits instead
> of 8 bits in RFC 3306, i.e. it updates 3306 which is already stated in
> there.

Can't we just say 3306 is updated by this new text, if it is approved?  We m=
ay not need to change 3306.

I think the same applies to RFcC3956 too, as bits 17-20 are reserved, and yo=
u're using those.  Actually also nteresting to read Appendix A of that RFC ;=
)

> Maybe in this draft we can say that we use RFC 3946 definition of the
> reserved field.
>=20
> BTW, in Teemu Kiviniemi's thesis on Implementation of an IPv4 to IPv6 Mult=
icast
> Translator
> ASM prefix: ff7e:140:2001:db8:ab:cd::/96
> is used, which matches Tim's suggestion :-).

Not quite, the above is ff7e:0140....
>=20
> This is the SSM prefix: ff3e::/96 that is used.

BTW, Stig had a v4/v6 multicast translator runnng ten years ago, worked quit=
e well!

Cheers,
Tim

>=20
> Behcet
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From wwwrun@rfc-editor.org  Mon Aug 20 19:17:55 2012
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6225E21F8473; Mon, 20 Aug 2012 19:17:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.312
X-Spam-Level: 
X-Spam-Status: No, score=-102.312 tagged_above=-999 required=5 tests=[AWL=0.288, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GvG2BREpB8Dx; Mon, 20 Aug 2012 19:17:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id F087F21F8472; Mon, 20 Aug 2012 19:17:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5702862188; Mon, 20 Aug 2012 19:16:06 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120821021606.5702862188@rfc-editor.org>
Date: Mon, 20 Aug 2012 19:16:06 -0700 (PDT)
Cc: mboned@ietf.org, rfc-editor@rfc-editor.org
Subject: [MBONED] RFC 6676 on Multicast Addresses for Documentation
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 02:17:55 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6676

        Title:      Multicast Addresses for Documentation 
        Author:     S. Venaas, R. Parekh,
                    G. Van de Velde, T. Chown,
                    M. Eubanks
        Status:     Informational
        Stream:     IETF
        Date:       August 2012
        Mailbox:    stig@cisco.com, 
                    riparekh@cisco.com, 
                    gvandeve@cisco.com,
                    tjc@ecs.soton.ac.uk, 
                    marshall.eubanks@iformata.com
        Pages:      7
        Characters: 14100
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mboned-mcaddrdoc-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6676.txt

This document discusses which multicast addresses should be used for
documentation purposes and reserves multicast addresses for such use.
Some multicast addresses are derived from AS numbers or unicast
addresses.  This document also explains how these can be used for
documentation purposes.  This document is not an Internet Standards 
Track specification; it is published for informational purposes.

This document is a product of the MBONE Deployment Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From jacni@jacni.com  Mon Aug 20 19:42:20 2012
Return-Path: <jacni@jacni.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6D3511E80AD for <mboned@ietfa.amsl.com>; Mon, 20 Aug 2012 19:42:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=1.031,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bv4PmTVkOtw4 for <mboned@ietfa.amsl.com>; Mon, 20 Aug 2012 19:42:20 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 07BEE11E80A5 for <mboned@ietf.org>; Mon, 20 Aug 2012 19:42:19 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so8160603pbb.31 for <mboned@ietf.org>; Mon, 20 Aug 2012 19:42:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:x-gm-message-state; bh=frqypjRpUFCRQqnYQEgriKTBoeNMiinvub06f5qKEVs=; b=IunVW1p1sA5tJkrrlOSQHs6HTTzRnKUzNik7Gcl5exnFp5qlsJFXtLWRm5DvlPxxN/ d0LP+HV+wkrzbcOz1ZqorspNGyIVjLHE5C6LJij1AmPo/eNwKOnq6AcoHssSk6WambrT qitxcJNTalVyM0sYJaYD9+j7WbMCZ9OvSilYKohWltdan/kqvQN5BD7ZONhOvxCC2BUD tv7jsYs4l8YCQxbAKuOh/+T8rl6/BhWbQeR68ykmLd9NIJuv3GjqzMgoz99cfsnMfUIo UqS4QH/Ue6lL2hhb0dWyyZwtyaiytjdeXGmBrBkgjKrSJoku0gYOmwebGMVi5Lsn6G11 i8QA==
Received: by 10.66.87.138 with SMTP id ay10mr34213859pab.38.1345516939584; Mon, 20 Aug 2012 19:42:19 -0700 (PDT)
Received: from [10.140.20.78] (64-104-125-217.cisco.com. [64.104.125.217]) by mx.google.com with ESMTPS id kc7sm402448pbb.5.2012.08.20.19.42.17 (version=SSLv3 cipher=OTHER); Mon, 20 Aug 2012 19:42:18 -0700 (PDT)
Message-ID: <5032F585.2000607@jacni.com>
Date: Tue, 21 Aug 2012 10:42:13 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com> <502AFECA.1090905@venaas.com> <2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <EMEW3|1c3fd9d33484c5343b2d7337b5211574o7G0Be03tjc|ecs.soton.ac.uk|2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <502E8819.5030901@venaas.com> <CAC8QAccRXZW=TUw3-6NSrOVy+t-iv9aqBGHzSP3tQw9_LD_S5g@mail.gmail.com> <502EA087.2050803@venaas.com> <CAC8QAccswaS3cTqAdoEUzb4hnFO+qd=cx71k5mdsbo5GJNx6LA@mail.gmail.com> <E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk> <EMEW3|b1f060ff67b81d8a57bf37f9620b398co7JNdl03tjc|ecs.soton.ac.uk|E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|b1f060ff67b81d8a57bf37f9620b398co7JNdl03tjc|ecs.soton.ac.uk|E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="------------070505010807070809060009"
X-Gm-Message-State: ALoCoQmufpvHT7w9rGCtmeDUQTDgUezzS6Mn5dJHhuu8UBqSWVBreEpC2bDMy0wkfQDIQEokKOzP
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 02:42:20 -0000

This is a multi-part message in MIME format.
--------------070505010807070809060009
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Tim,

On 8/21/2012 Tuesday 6:39 AM, Tim Chown wrote:
> ..
> .
>> Why?
>> As far as I understand, the issue here is to use which bit in the
>> reserved field, Tim suggested the rightmost and your proposal uses the
>> leftmost.
>> RFC3946 solves this problem by redefining rsvd field as 4 bits instead
>> of 8 bits in RFC 3306, i.e. it updates 3306 which is already stated in
>> there.
> Can't we just say 3306 is updated by this new text, if it is approved?  We may not need to change 3306.
Agree.

>
> I think the same applies to RFcC3956 too, as bits 17-20 are reserved, and you're using those.  Actually also nteresting to read Appendix A of that RFC ;)
I guess we won't need a "RFC3956 updated", since Appendix A just says, "

    Instead of using flags bits ("FF70::/12"), one could have used the
    leftmost reserved bits instead ("FF3x:8000::/17").
"

and doesn't say anything about the 4bit rsvd elsewhere.

Or I misunderstand it?


Cheers,
Jacni

>> Maybe in this draft we can say that we use RFC 3946 definition of the
>> reserved field.
>>
>> BTW, in Teemu Kiviniemi's thesis on Implementation of an IPv4 to IPv6 Multicast
>> Translator
>> ASM prefix: ff7e:140:2001:db8:ab:cd::/96
>> is used, which matches Tim's suggestion :-).
> Not quite, the above is ff7e:0140....
>> This is the SSM prefix: ff3e::/96 that is used.
> BTW, Stig had a v4/v6 multicast translator runnng ten years ago, worked quite well!
>
> Cheers,
> Tim
>
>> Behcet
>> _______________________________________________
>> MBONED mailing list
>> MBONED@ietf.org
>> https://www.ietf.org/mailman/listinfo/mboned
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>


--------------070505010807070809060009
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <font face="Calibri">Hi Tim,<br>
      <br>
    </font>
    <div class="moz-cite-prefix">On 8/21/2012 Tuesday 6:39 AM, Tim Chown
      wrote:<br>
    </div>
    <blockquote
cite="mid:EMEW3|b1f060ff67b81d8a57bf37f9620b398co7JNdl03tjc|ecs.soton.ac.uk|E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk"
      type="cite">..
      <pre wrap="">.
</pre>
      <blockquote type="cite">
        <pre wrap="">
Why?
As far as I understand, the issue here is to use which bit in the
reserved field, Tim suggested the rightmost and your proposal uses the
leftmost.
RFC3946 solves this problem by redefining rsvd field as 4 bits instead
of 8 bits in RFC 3306, i.e. it updates 3306 which is already stated in
there.
</pre>
      </blockquote>
      <pre wrap="">
Can't we just say 3306 is updated by this new text, if it is approved?  We may not need to change 3306.</pre>
    </blockquote>
    Agree.<br>
    <br>
    <blockquote
cite="mid:EMEW3|b1f060ff67b81d8a57bf37f9620b398co7JNdl03tjc|ecs.soton.ac.uk|E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk"
      type="cite">
      <pre wrap="">

I think the same applies to RFcC3956 too, as bits 17-20 are reserved, and you're using those.  Actually also nteresting to read Appendix A of that RFC ;)
</pre>
    </blockquote>
    I guess we won't need a "RFC3956 updated", since Appendix A just
    says, "<br>
    <pre class="newpage">   Instead of using flags bits ("FF70::/12"), one could have used the
   leftmost reserved bits instead ("FF3x:8000::/17").
"
</pre>
    and doesn't say anything about the 4bit rsvd elsewhere.<br>
    <br>
    Or I misunderstand it?<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
cite="mid:EMEW3|b1f060ff67b81d8a57bf37f9620b398co7JNdl03tjc|ecs.soton.ac.uk|E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk"
      type="cite">
      <pre wrap="">
</pre>
      <blockquote type="cite">
        <pre wrap="">Maybe in this draft we can say that we use RFC 3946 definition of the
reserved field.

BTW, in Teemu Kiviniemi's thesis on Implementation of an IPv4 to IPv6 Multicast
Translator
ASM prefix: ff7e:140:2001:db8:ab:cd::/96
is used, which matches Tim's suggestion :-).
</pre>
      </blockquote>
      <pre wrap="">
Not quite, the above is ff7e:0140....
</pre>
      <blockquote type="cite">
        <pre wrap="">
This is the SSM prefix: ff3e::/96 that is used.
</pre>
      </blockquote>
      <pre wrap="">
BTW, Stig had a v4/v6 multicast translator runnng ten years ago, worked quite well!

Cheers,
Tim

</pre>
      <blockquote type="cite">
        <pre wrap="">
Behcet
_______________________________________________
MBONED mailing list
<a class="moz-txt-link-abbreviated" href="mailto:MBONED@ietf.org">MBONED@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mboned">https://www.ietf.org/mailman/listinfo/mboned</a>
</pre>
      </blockquote>
      <pre wrap="">_______________________________________________
MBONED mailing list
<a class="moz-txt-link-abbreviated" href="mailto:MBONED@ietf.org">MBONED@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mboned">https://www.ietf.org/mailman/listinfo/mboned</a>

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------070505010807070809060009--

From sarikaya2012@gmail.com  Tue Aug 21 08:55:45 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 748FC21F8787 for <mboned@ietfa.amsl.com>; Tue, 21 Aug 2012 08:55:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.605
X-Spam-Level: 
X-Spam-Status: No, score=-3.605 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i+X8kZtsr9la for <mboned@ietfa.amsl.com>; Tue, 21 Aug 2012 08:55:45 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id BB72621F84FE for <mboned@ietf.org>; Tue, 21 Aug 2012 08:55:44 -0700 (PDT)
Received: by yenm5 with SMTP id m5so6568092yen.31 for <mboned@ietf.org>; Tue, 21 Aug 2012 08:55:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=DClDM7KkttD8hg734W4X10rMLbayNiOd2ZGqTLhg1W8=; b=wCC1z/BoJdi/2h9G2OkaC8m/xCzQ8/1OEQVumGvc76qe/hK6dfQ88EblyTNjSrpSxQ j4z8NTvd5GTHn2mNEPz8KH91DMqHzlNeA4naP5wCAJBqVexlxFQiGYBRhTvy0wjLgc+d ryuhYdxscLC43RKsavmwtuRYOKvOYLZTE0Ii7tD5C2IO7HQ73k1gZh/95wqLEkSZ8zj9 IxxVFCCUTOeGEUKVD2MNNqRdvVAxgDAm6/pu/dXDjcR+lKyMhE9q6uoFucmruFbLl2QL r2qBLHL83JOcff+hWysNt3SOzKit1xqZd04S/mHWUsYjv32y7D+wNarj1+QkWvuQ7vHu iKmw==
MIME-Version: 1.0
Received: by 10.50.159.226 with SMTP id xf2mr13761489igb.41.1345564543489; Tue, 21 Aug 2012 08:55:43 -0700 (PDT)
Received: by 10.231.55.70 with HTTP; Tue, 21 Aug 2012 08:55:43 -0700 (PDT)
In-Reply-To: <EMEW3|b1f060ff67b81d8a57bf37f9620b398co7JNdl03tjc|ecs.soton.ac.uk|E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk>
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com> <502AFECA.1090905@venaas.com> <2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <EMEW3|1c3fd9d33484c5343b2d7337b5211574o7G0Be03tjc|ecs.soton.ac.uk|2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <502E8819.5030901@venaas.com> <CAC8QAccRXZW=TUw3-6NSrOVy+t-iv9aqBGHzSP3tQw9_LD_S5g@mail.gmail.com> <502EA087.2050803@venaas.com> <E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk> <CAC8QAccswaS3cTqAdoEUzb4hnFO+qd=cx71k5mdsbo5GJNx6LA@mail.gmail.com> <EMEW3|b1f060ff67b81d8a57bf37f9620b398co7JNdl03tjc|ecs.soton.ac.uk|E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk>
Date: Tue, 21 Aug 2012 10:55:43 -0500
Message-ID: <CAC8QAce3dAaBEdtenLWUQMcxE-PSzRvWgaYcDD214y=PMUwO_g@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 15:55:45 -0000

Hi Tim,


>> As far as I understand, the issue here is to use which bit in the
>> reserved field, Tim suggested the rightmost and your proposal uses the
>> leftmost.
>> RFC3946 solves this problem by redefining rsvd field as 4 bits instead
>> of 8 bits in RFC 3306, i.e. it updates 3306 which is already stated in
>> there.
>
> Can't we just say 3306 is updated by this new text, if it is approved?  We may not need to change 3306.
>
> I think the same applies to RFcC3956 too, as bits 17-20 are reserved, and you're using those.  Actually also nteresting to read Appendix A of that RFC ;)
>

Yes, I read. Maybe you missed my point: if we use RFC 3956 and state
it clearly, updating RFC 3306 is going to be implicit in this
normative use.

>> Maybe in this draft we can say that we use RFC 3946 definition of the
>> reserved field.
>>
>> BTW, in Teemu Kiviniemi's thesis on Implementation of an IPv4 to IPv6 Multicast
>> Translator
>> ASM prefix: ff7e:140:2001:db8:ab:cd::/96
>> is used, which matches Tim's suggestion :-).
>
> Not quite, the above is ff7e:0140....

Sorry, I confused the bits.
But the above address seemed to have worked as well. I think that is
the point here.

>>
>> This is the SSM prefix: ff3e::/96 that is used.


My suggestion is to define the ASM prefix as either ff70::/12 or as
ff3x:8000/17 this way we align the prefix with the embedded RP prefix.

Regards,

Behcet

From tjc@ecs.soton.ac.uk  Tue Aug 21 09:09:22 2012
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9395B21F86C8 for <mboned@ietfa.amsl.com>; Tue, 21 Aug 2012 09:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.424
X-Spam-Level: 
X-Spam-Status: No, score=-2.424 tagged_above=-999 required=5 tests=[AWL=0.174,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ZbMon3eUZIZ for <mboned@ietfa.amsl.com>; Tue, 21 Aug 2012 09:09:21 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF9621F869E for <mboned@ietf.org>; Tue, 21 Aug 2012 09:09:21 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q7LG9Ijs029626 for <mboned@ietf.org>; Tue, 21 Aug 2012 17:09:18 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk q7LG9Ijs029626
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1345565359; bh=6fcwai4gYXW7/XR3tM7jHpRj90M=; h=From:Mime-Version:Subject:Date:References:To:In-Reply-To; b=sqtSY5DPnjTyGX6FJ/r/9ezn4qIRqHpdSmYi9MWKc21RyKwmGqpNpg5o6WyWhC+C1 693n8AB9XUVyAcmG35g13xG7zwNROeGGTGzmtBGaGXsf5Q+In5A3sPL+IRiEAWjL4P 83Q/aBRom2qIVtBFaEveLV0/wuoq6zeveBw0nbHQ=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id o7KH9I04306282743w ret-id none; Tue, 21 Aug 2012 17:09:18 +0100
Received: from ip-205-231.eduroam.soton.ac.uk (ip-205-231.eduroam.soton.ac.uk [152.78.205.231]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q7LG9F6U026631 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <mboned@ietf.org>; Tue, 21 Aug 2012 17:09:15 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F75DE86D-DFEF-40DF-852C-55EDA03E465B"
Message-ID: <EMEW3|9080010046043a3b61cd9da8e6360ea9o7KH9I03tjc|ecs.soton.ac.uk|C01BCCDC-7BE5-40FF-850E-6922E990E5B3@ecs.soton.ac.uk>
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Date: Tue, 21 Aug 2012 17:09:15 +0100
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com> <502AFECA.1090905@venaas.com> <2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <EMEW3|1c3fd9d33484c5343b2d7337b5211574o7G0Be03tjc|ecs.soton.ac.uk|2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <502E8819.5030901@venaas.com> <CAC8QAccRXZW=TUw3-6NSrOVy+t-iv9aqBGHzSP3tQw9_LD_S5g@mail.gmail.com> <502EA087.2050803@venaas.com> <CAC8QAccswaS3cTqAdoEUzb4hnFO+qd=cx71k5mdsbo5GJNx6LA@mail.gmail.com> <E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk> <EMEW3|b1f060ff67b81d8a57bf37f9620b398co7JNdl03tjc|ecs.soton.ac.uk|E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk> <5032F585.2000607@jacni.com> <C01BCCDC-7BE5-40FF-850E-6922E990E5B3@ecs.soton.ac.uk>
To: mboned@ietf.org
In-Reply-To: <5032F585.2000607@jacni.com>
X-Mailer: Apple Mail (2.1485)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=o7KH9I043062827400; tid=o7KH9I04306282743w; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: q7LG9Ijs029626
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Aug 2012 16:09:22 -0000

--Apple-Mail=_F75DE86D-DFEF-40DF-852C-55EDA03E465B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On 21 Aug 2012, at 03:42, Jacni Qin <jacni@jacni.com> wrote:

> Hi Tim,
>=20
> On 8/21/2012 Tuesday 6:39 AM, Tim Chown wrote:
>> I think the same applies to RFcC3956 too, as bits 17-20 are reserved, =
and you're using those.  Actually also nteresting to read Appendix A of =
that RFC ;)
> I guess we won't need a "RFC3956 updated", since Appendix A just says, =
"
>    Instead of using flags bits ("FF70::/12"), one could have used the
>    leftmost reserved bits instead ("FF3x:8000::/17").
> "
> and doesn't say anything about the 4bit rsvd elsewhere.
>=20
> Or I misunderstand it?

I'm not sure what the proper process is here.  My point was just that =
RFC3956 states that bits 17-20 are reserved, but the proposed range of =
addresses used by this draft involves setting a bit within that range, =
hence we should have an "updated by" note.  Also that RFC3956, unlike =
RFC3306, doesn't explicitly say the reserved bits must be set to zero. =20=


The irony of Appendix A of RFC3956 is that it mentioned that one could =
have used precisely the same range of addresses for Embedded-RP as is =
proposed for this draft, but instead a flag bit was used.

In response to Behcet's email, I agree the update(s) is/are implicit.=20

Tim


--Apple-Mail=_F75DE86D-DFEF-40DF-852C-55EDA03E465B
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 21 Aug 2012, at 03:42, Jacni Qin &lt;<a href="mailto:jacni@jacni.com">jacni@jacni.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
  
    <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
  
  <div text="#000000" bgcolor="#FFFFFF">
    <font face="Calibri">Hi Tim,<br>
      <br>
    </font>
    <div class="moz-cite-prefix">On 8/21/2012 Tuesday 6:39 AM, Tim Chown
      wrote:</div><blockquote cite="mid:EMEW3|b1f060ff67b81d8a57bf37f9620b398co7JNdl03tjc|ecs.soton.ac.uk|E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk" type="cite"><pre wrap="">I think the same applies to RFcC3956 too, as bits 17-20 are reserved, and you're using those.  Actually also nteresting to read Appendix A of that RFC ;)
</pre>
    </blockquote>
    I guess we won't need a "RFC3956 updated", since Appendix A just
    says, "<br>
    <pre class="newpage">   Instead of using flags bits ("FF70::/12"), one could have used the
   leftmost reserved bits instead ("FF3x:8000::/17").
"
</pre>
    and doesn't say anything about the 4bit rsvd elsewhere.<br>
    <br>
    Or I misunderstand it?<br></div></blockquote><div><br></div>I'm not sure what the proper process is here. &nbsp;My point was just that RFC3956 states that bits 17-20 are reserved, but the proposed range of addresses used by this draft involves setting a bit within that range, hence we should have an "updated by" note. &nbsp;Also that RFC3956, unlike RFC3306, doesn't explicitly say the reserved bits must be set to zero. &nbsp;</div><div><br></div><div>The irony of Appendix A of RFC3956 is that it mentioned that one could have used precisely the same range of addresses for Embedded-RP as is proposed for this draft, but instead a flag bit was used.</div><div><br></div><div>In response to Behcet's email, I agree the update(s) is/are implicit.&nbsp;</div><div><br></div><div>Tim</div><div><br></div></body></html>
--Apple-Mail=_F75DE86D-DFEF-40DF-852C-55EDA03E465B--

From jacni@jacni.com  Wed Aug 22 21:07:14 2012
Return-Path: <jacni@jacni.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACC7F21F8585 for <mboned@ietfa.amsl.com>; Wed, 22 Aug 2012 21:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[AWL=0.988,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FiEg8GujKsLd for <mboned@ietfa.amsl.com>; Wed, 22 Aug 2012 21:07:13 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0DD8621F857D for <mboned@ietf.org>; Wed, 22 Aug 2012 21:07:12 -0700 (PDT)
Received: by dadf8 with SMTP id f8so173186dad.31 for <mboned@ietf.org>; Wed, 22 Aug 2012 21:07:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:x-gm-message-state; bh=ZCYt2Ad3Fu5wmCZVZvlcMXmru+tGyvBF0elsc0c3R9E=; b=RxCjt3UeaCiOamUAyZsJ0JrgC9OqEW6F4WDxmYFBpkiBwjpLSETByy29Sr0xji14wJ zaoS7YqcB9Z6w9AaY5virgdPTn2IAgVLg/9dTyRULFUKaKCuAAFBrvWA+eHKX4sT5tF7 8wdA8JLpTcyNMRdLjZje2+hDxMXx6pp/m3cJV55neDUtOaiMUaqXyl4P3GZnw4k+5+IN 5YA5M2Xp790ZTDxTG7fisnx8o3gl7zL2FPPSGC0RboLxti4qG+QqJSSPSgD5bPapQFrI 7qpaSpHLU2AggwkrgBCE+qzc7cjIUGsTiqJ2sBEI1KaSBku6LHIZfQRrttJ6Uyo67n6I I4Kg==
Received: by 10.66.87.66 with SMTP id v2mr174659paz.71.1345694832114; Wed, 22 Aug 2012 21:07:12 -0700 (PDT)
Received: from [10.140.16.196] (64-104-125-217.cisco.com. [64.104.125.217]) by mx.google.com with ESMTPS id io1sm5070895pbc.67.2012.08.22.21.07.07 (version=SSLv3 cipher=OTHER); Wed, 22 Aug 2012 21:07:11 -0700 (PDT)
Message-ID: <5035AC65.4060301@jacni.com>
Date: Thu, 23 Aug 2012 12:07:01 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com> <502AFECA.1090905@venaas.com> <2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <EMEW3|1c3fd9d33484c5343b2d7337b5211574o7G0Be03tjc|ecs.soton.ac.uk|2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <502E8819.5030901@venaas.com> <CAC8QAccRXZW=TUw3-6NSrOVy+t-iv9aqBGHzSP3tQw9_LD_S5g@mail.gmail.com> <502EA087.2050803@venaas.com> <CAC8QAccswaS3cTqAdoEUzb4hnFO+qd=cx71k5mdsbo5GJNx6LA@mail.gmail.com> <E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk> <EMEW3|b1f060ff67b81d8a57bf37f9620b398co7JNdl03tjc|ecs.soton.ac.uk|E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk> <5032F585.2000607@jacni.com> <C01BCCDC-7BE5-40FF-850E-6922E990E5B3@ecs.soton.ac.uk> <EMEW3|9080010046043a3b61cd9da8e6360ea9o7KH9I03tjc|ecs.soton.ac.uk|C01BCCDC-7BE5-40FF-850E-6922E990E5B3@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|9080010046043a3b61cd9da8e6360ea9o7KH9I03tjc|ecs.soton.ac.uk|C01BCCDC-7BE5-40FF-850E-6922E990E5B3@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="------------020206020708070607060008"
X-Gm-Message-State: ALoCoQkE4T+le38vX95BAMa4sedPOmSSHvhzoIkKzcPlp1XZYrdX1kXh6LFKpymjD2PEhBkEcCUx
Cc: mboned@ietf.org
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Aug 2012 04:07:14 -0000

This is a multi-part message in MIME format.
--------------020206020708070607060008
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


On 8/22/2012 Wednesday 12:09 AM, Tim Chown wrote:
> On 21 Aug 2012, at 03:42, Jacni Qin <jacni@jacni.com 
> <mailto:jacni@jacni.com>> wrote:
>
>> Hi Tim,
>>
>> On 8/21/2012 Tuesday 6:39 AM, Tim Chown wrote:
>>> I think the same applies to RFcC3956 too, as bits 17-20 are reserved, and you're using those.  Actually also nteresting to read Appendix A of that RFC ;)
>> I guess we won't need a "RFC3956 updated", since Appendix A just says, "
>>     Instead of using flags bits ("FF70::/12"), one could have used the
>>     leftmost reserved bits instead ("FF3x:8000::/17").
>> "
>> and doesn't say anything about the 4bit rsvd elsewhere.
>>
>> Or I misunderstand it?
>
> I'm not sure what the proper process is here.  My point was just that 
> RFC3956 states that bits 17-20 are reserved,
The 3956 doesn't really make that statement on the 4 bits itself, 
instead, more like inheriting from 3306.
While I don't think this issue matters that much technically, we can 
follow a proper process if anyone have one.

> but the proposed range of addresses used by this draft involves 
> setting a bit within that range, hence we should have an "updated by" 
> note.  Also that RFC3956, unlike RFC3306, doesn't explicitly say the 
> reserved bits must be set to zero.
>
> The irony of Appendix A of RFC3956 is that it mentioned that one could 
> have used precisely the same range of addresses for Embedded-RP as is 
> proposed for this draft, but instead a flag bit was used.
So, following this logic, we'll be perfectly fine using a flag. ;-)


Cheers,
Jacni

>
> In response to Behcet's email, I agree the update(s) is/are implicit.
>
> Tim
>
>
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned


--------------020206020708070607060008
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <div class="moz-cite-prefix">On 8/22/2012 Wednesday 12:09 AM, Tim
      Chown wrote:<br>
    </div>
    <blockquote
cite="mid:EMEW3|9080010046043a3b61cd9da8e6360ea9o7KH9I03tjc|ecs.soton.ac.uk|C01BCCDC-7BE5-40FF-850E-6922E990E5B3@ecs.soton.ac.uk"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div>
        <div>On 21 Aug 2012, at 03:42, Jacni Qin &lt;<a
            moz-do-not-send="true" href="mailto:jacni@jacni.com">jacni@jacni.com</a>&gt;
          wrote:</div>
        <br class="Apple-interchange-newline">
        <blockquote type="cite">
          <meta content="text/html; charset=ISO-8859-1"
            http-equiv="Content-Type">
          <div text="#000000" bgcolor="#FFFFFF"> <font face="Calibri">Hi
              Tim,<br>
              <br>
            </font>
            <div class="moz-cite-prefix">On 8/21/2012 Tuesday 6:39 AM,
              Tim Chown wrote:</div>
            <blockquote
cite="mid:EMEW3|b1f060ff67b81d8a57bf37f9620b398co7JNdl03tjc|ecs.soton.ac.uk|E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk"
              type="cite">
              <pre wrap="">I think the same applies to RFcC3956 too, as bits 17-20 are reserved, and you're using those.  Actually also nteresting to read Appendix A of that RFC ;)
</pre>
            </blockquote>
            I guess we won't need a "RFC3956 updated", since Appendix A
            just says, "<br>
            <pre class="newpage">   Instead of using flags bits ("FF70::/12"), one could have used the
   leftmost reserved bits instead ("FF3x:8000::/17").
"
</pre>
            and doesn't say anything about the 4bit rsvd elsewhere.<br>
            <br>
            Or I misunderstand it?<br>
          </div>
        </blockquote>
        <div><br>
        </div>
        I'm not sure what the proper process is here. &nbsp;My point was just
        that RFC3956 states that bits 17-20 are reserved, </div>
    </blockquote>
    The 3956 doesn't really make that statement on the 4 bits itself,
    instead, more like inheriting from 3306.<br>
    While I don't think this issue matters that much technically, we can
    follow a proper process if anyone have one.<br>
    <br>
    <blockquote
cite="mid:EMEW3|9080010046043a3b61cd9da8e6360ea9o7KH9I03tjc|ecs.soton.ac.uk|C01BCCDC-7BE5-40FF-850E-6922E990E5B3@ecs.soton.ac.uk"
      type="cite">
      <div>but the proposed range of addresses used by this draft
        involves setting a bit within that range, hence we should have
        an "updated by" note. &nbsp;Also that RFC3956, unlike RFC3306,
        doesn't explicitly say the reserved bits must be set to zero. &nbsp;</div>
      <div><br>
      </div>
      <div>The irony of Appendix A of RFC3956 is that it mentioned that
        one could have used precisely the same range of addresses for
        Embedded-RP as is proposed for this draft, but instead a flag
        bit was used.</div>
    </blockquote>
    So, following this logic, we'll be perfectly fine using a flag. ;-)<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote
cite="mid:EMEW3|9080010046043a3b61cd9da8e6360ea9o7KH9I03tjc|ecs.soton.ac.uk|C01BCCDC-7BE5-40FF-850E-6922E990E5B3@ecs.soton.ac.uk"
      type="cite">
      <div><br>
      </div>
      <div>In response to Behcet's email, I agree the update(s) is/are
        implicit.&nbsp;</div>
      <div><br>
      </div>
      <div>Tim</div>
      <div><br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
MBONED mailing list
<a class="moz-txt-link-abbreviated" href="mailto:MBONED@ietf.org">MBONED@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mboned">https://www.ietf.org/mailman/listinfo/mboned</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------020206020708070607060008--

From mohamed.boucadair@orange.com  Thu Aug 23 02:29:30 2012
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB0A721F8593 for <mboned@ietfa.amsl.com>; Thu, 23 Aug 2012 02:29:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.054
X-Spam-Level: 
X-Spam-Status: No, score=-2.054 tagged_above=-999 required=5 tests=[AWL=0.193,  BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DKZB9pQGF51A for <mboned@ietfa.amsl.com>; Thu, 23 Aug 2012 02:29:30 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id EFD0121F8491 for <mboned@ietf.org>; Thu, 23 Aug 2012 02:29:29 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm09.si.francetelecom.fr (ESMTP service) with ESMTP id 0AB3B2DCCD8; Thu, 23 Aug 2012 11:29:29 +0200 (CEST)
Received: from PUEXCH21.nanterre.francetelecom.fr (unknown [10.101.44.28]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id D617A23805C; Thu, 23 Aug 2012 11:29:28 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH21.nanterre.francetelecom.fr ([10.101.44.28]) with mapi; Thu, 23 Aug 2012 11:29:07 +0200
From: <mohamed.boucadair@orange.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Date: Thu, 23 Aug 2012 11:29:06 +0200
Thread-Topic: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
Thread-Index: Ac1/t0pEus01e6haQoiz5poxD8SpqQBWbtPQ
Message-ID: <94C682931C08B048B7A8645303FDC9F36E5332A7CB@PUEXCB1B.nanterre.francetelecom.fr>
References: <E3FAB1F4F41F3A45B287E8D9C53522FD379D374F@PACDCEXMB05.cable.comcast.com> <502AFECA.1090905@venaas.com> <2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <EMEW3|1c3fd9d33484c5343b2d7337b5211574o7G0Be03tjc|ecs.soton.ac.uk|2B337C44-D16B-49BD-9347-901F6107A239@ecs.soton.ac.uk> <502E8819.5030901@venaas.com> <CAC8QAccRXZW=TUw3-6NSrOVy+t-iv9aqBGHzSP3tQw9_LD_S5g@mail.gmail.com> <502EA087.2050803@venaas.com> <CAC8QAccswaS3cTqAdoEUzb4hnFO+qd=cx71k5mdsbo5GJNx6LA@mail.gmail.com> <E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk> <EMEW3|b1f060ff67b81d8a57bf37f9620b398co7JNdl03tjc|ecs.soton.ac.uk|E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk> <5032F585.2000607@jacni.com> <C01BCCDC-7BE5-40FF-850E-6922E990E5B3@ecs.soton.ac.uk> <EMEW3|9080010046043a3b61cd9da8e6360ea9o7KH9I03tjc|ecs.soton.ac.uk|C01BCCDC-7BE5-40FF-850E-6922E990E5B3@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|9080010046043a3b61cd9da8e6360ea9o7KH9I03tjc|ecs.soton.ac.uk|C01BCCDC-7BE5-40FF-850E-6922E990E5B3@ecs.soton.ac.uk>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: multipart/alternative; boundary="_000_94C682931C08B048B7A8645303FDC9F36E5332A7CBPUEXCB1Bnante_"
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.8.23.73314
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Aug 2012 09:29:31 -0000

--_000_94C682931C08B048B7A8645303FDC9F36E5332A7CBPUEXCB1Bnante_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear Tim,

I agree with you an update note is needed to be added to the draft for 3306=
 and 3956. The consequence of this change, and in order to accommodate futu=
re extensions, I have changed also the text for ASM mode to reserve a bit a=
nd not a prefix. I see this as an incentive for applications to check the b=
it and not match a prefix.

For the SSM mode, I maintained the same /96 as in -03.

I will submit a new version with these new changes (+ other minor modificat=
ions).

Thanks.

Cheers,
Med


________________________________
De : mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] De la part de=
 Tim Chown
Envoy=E9 : mardi 21 ao=FBt 2012 18:09
=C0 : mboned@ietf.org
Objet : Re: [MBONED] draft-ietf-mboned-64-multicast-address-format-03.txt

On 21 Aug 2012, at 03:42, Jacni Qin <jacni@jacni.com<mailto:jacni@jacni.com=
>> wrote:

Hi Tim,

On 8/21/2012 Tuesday 6:39 AM, Tim Chown wrote:

I think the same applies to RFcC3956 too, as bits 17-20 are reserved, and y=
ou're using those.  Actually also nteresting to read Appendix A of that RFC=
 ;)


I guess we won't need a "RFC3956 updated", since Appendix A just says, "

   Instead of using flags bits ("FF70::/12"), one could have used the
   leftmost reserved bits instead ("FF3x:8000::/17").
"


and doesn't say anything about the 4bit rsvd elsewhere.

Or I misunderstand it?

I'm not sure what the proper process is here.  My point was just that RFC39=
56 states that bits 17-20 are reserved, but the proposed range of addresses=
 used by this draft involves setting a bit within that range, hence we shou=
ld have an "updated by" note.  Also that RFC3956, unlike RFC3306, doesn't e=
xplicitly say the reserved bits must be set to zero.

The irony of Appendix A of RFC3956 is that it mentioned that one could have=
 used precisely the same range of addresses for Embedded-RP as is proposed =
for this draft, but instead a flag bit was used.

In response to Behcet's email, I agree the update(s) is/are implicit.

Tim


--_000_94C682931C08B048B7A8645303FDC9F36E5332A7CBPUEXCB1Bnante_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18702"></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-brea=
k: after-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186572309-23082012><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">Dear Tim,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186572309-23082012><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186572309-23082012><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">I agree with you an update note is needed to =
be added=20
to the draft for 3306 and 3956. The consequence of this change, and in orde=
r to=20
accommodate future extensions, I have changed also the text for ASM mode to=
=20
reserve a bit and not a prefix. I see this as an incentive for applications=
 to=20
check the bit and not match a prefix.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186572309-23082012><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New"></FONT></SPAN><SPAN class=3D186572309-2308201=
2><FONT=20
color=3D#0000ff size=3D2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186572309-23082012><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">For the SSM mode, I maintained the same /96 a=
s in=20
-03.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186572309-23082012><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186572309-23082012><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">I will submit a new version with these new ch=
anges (+=20
other minor modifications). </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186572309-23082012><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186572309-23082012><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">Thanks. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186572309-23082012><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186572309-23082012><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">Cheers,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186572309-23082012><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New">Med</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D186572309-23082012><FONT color=3D=
#0000ff=20
size=3D2 face=3D"Courier New"></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5p=
x; MARGIN-RIGHT: 0px"=20
dir=3Dltr>
  <DIV dir=3Dltr lang=3Dfr class=3DOutlookMessageHeader align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT size=3D2 face=3DTahoma><B>De&nbsp;:</B> mboned-bounces@ietf.org=20
  [mailto:mboned-bounces@ietf.org] <B>De la part de</B> Tim=20
  Chown<BR><B>Envoy=E9&nbsp;:</B> mardi 21 ao=FBt 2012 18:09<BR><B>=C0&nbsp=
;:</B>=20
  mboned@ietf.org<BR><B>Objet&nbsp;:</B> Re: [MBONED]=20
  draft-ietf-mboned-64-multicast-address-format-03.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV>
  <DIV>On 21 Aug 2012, at 03:42, Jacni Qin &lt;<A=20
  href=3D"mailto:jacni@jacni.com">jacni@jacni.com</A>&gt; wrote:</DIV><BR=20
  class=3DApple-interchange-newline>
  <BLOCKQUOTE type=3D"cite">
    <DIV bgcolor=3D"#FFFFFF" text=3D"#000000"><FONT face=3DCalibri>Hi=20
    Tim,<BR><BR></FONT>
    <DIV class=3Dmoz-cite-prefix>On 8/21/2012 Tuesday 6:39 AM, Tim Chown=20
    wrote:</DIV>
    <BLOCKQUOTE=20
    cite=3Dmid:EMEW3|b1f060ff67b81d8a57bf37f9620b398co7JNdl03tjc|ecs.soton.=
ac.uk|E3E93136-7F2F-40B8-BC3B-CA7C9DC25F42@ecs.soton.ac.uk=20
    type=3D"cite"><PRE wrap=3D"">I think the same applies to RFcC3956 too, =
as bits 17-20 are reserved, and you're using those.  Actually also nteresti=
ng to read Appendix A of that RFC ;)
</PRE></BLOCKQUOTE>I guess we won't need a "RFC3956 updated", since Appendi=
x=20
    A just says, "<BR><PRE class=3Dnewpage>   Instead of using flags bits (=
"FF70::/12"), one could have used the
   leftmost reserved bits instead ("FF3x:8000::/17").
"
</PRE>and doesn't say anything about the 4bit rsvd elsewhere.<BR><BR>Or I=20
    misunderstand it?<BR></DIV></BLOCKQUOTE>
  <DIV><BR></DIV>I'm not sure what the proper process is here. &nbsp;My poi=
nt=20
  was just that RFC3956 states that bits 17-20 are reserved, but the propos=
ed=20
  range of addresses used by this draft involves setting a bit within that=
=20
  range, hence we should have an "updated by" note. &nbsp;Also that RFC3956=
,=20
  unlike RFC3306, doesn't explicitly say the reserved bits must be set to z=
ero.=20
  &nbsp;</DIV>
  <DIV><BR></DIV>
  <DIV>The irony of Appendix A of RFC3956 is that it mentioned that one cou=
ld=20
  have used precisely the same range of addresses for Embedded-RP as is pro=
posed=20
  for this draft, but instead a flag bit was used.</DIV>
  <DIV><BR></DIV>
  <DIV>In response to Behcet's email, I agree the update(s) is/are=20
  implicit.&nbsp;</DIV>
  <DIV><BR></DIV>
  <DIV>Tim</DIV>
  <DIV><BR></DIV></BLOCKQUOTE></BODY></HTML>

--_000_94C682931C08B048B7A8645303FDC9F36E5332A7CBPUEXCB1Bnante_--

From yiu_lee@cable.comcast.com  Thu Aug 23 13:37:10 2012
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2CBF21F854A for <mboned@ietfa.amsl.com>; Thu, 23 Aug 2012 13:37:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.263
X-Spam-Level: 
X-Spam-Status: No, score=-104.263 tagged_above=-999 required=5 tests=[AWL=0.968, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b2Cs4-9yjit9 for <mboned@ietfa.amsl.com>; Thu, 23 Aug 2012 13:37:08 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF1B21F8549 for <mboned@ietf.org>; Thu, 23 Aug 2012 13:37:05 -0700 (PDT)
Received: from ([24.40.56.115]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.30532839; Thu, 23 Aug 2012 14:16:40 -0600
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.115]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0309.002; Thu, 23 Aug 2012 16:36:58 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: [Softwires] draft-ietf-softwire-dslite-multicast-03
Thread-Index: AQHNgW8KcaL1fN3wB0GMHsBgJpBNYQ==
Date: Thu, 23 Aug 2012 20:36:57 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD379E57CD@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E5332A8E5@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [24.40.55.70]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3428584616_125724"
MIME-Version: 1.0
Subject: [MBONED] FW: [Softwires] draft-ietf-softwire-dslite-multicast-03
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Aug 2012 20:37:10 -0000

--B_3428584616_125724
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Hi,

We submitted a revision of softwire-dslite-multicast to WGLC. This draft
would use the mboned-64-multicast-address-format. We would like this WG to
review this draft and give us feedback.

Thanks,
Yiu


On 8/23/12 10:54 AM, "mohamed.boucadair@orange.com"
<mohamed.boucadair@orange.com> wrote:

>Dear all,
>
>A new version taking into account comments received during the WGLC has
>been submitted. The main changes are:
>
>* change the title
>* clarify the solution is generic for any 4-6-4 use case and the solution
>has been designed with DS-Lite in mind
>* add a discussion about scoping: preserve the scope when translation
>multicast addresses
>* add a note only IPv4-in-IPv6 encap is detailed in the document but
>other tunnelling techniques may be defined in the future
>* update the security section with some discussions related to scoping.
>* + other editorial changes.
>
>To view the detailed changes:
>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-softwire-dslite-multicast-03
>
>I hope this version solve the concerns raised during the WGLC.
>
>Cheers,
>Med
>
>
>>-----Message d'origine-----
>>De : softwires-bounces@ietf.org
>>[mailto:softwires-bounces@ietf.org] De la part de
>>internet-drafts@ietf.org
>>Envoy=E9 : jeudi 23 ao=FBt 2012 16:47
>>=C0 : i-d-announce@ietf.org
>>Cc : softwires@ietf.org
>>Objet : [Softwires] I-D Action:
>>draft-ietf-softwire-dslite-multicast-03.txt
>>
>>
>>A New Internet-Draft is available from the on-line
>>Internet-Drafts directories.
>> This draft is a work item of the Softwires Working Group of the IETF.
>>
>>	Title           : Delivery of IPv4 Multicast Services
>>to IPv4 Clients over an IPv6 Multicast Network
>>	Author(s)       : Jacni Qin
>>                          Mohamed Boucadair
>>                          Christian Jacquenet
>>                          Yiu L. Lee
>>                          Qian Wang
>>	Filename        : draft-ietf-softwire-dslite-multicast-03.txt
>>	Pages           : 20
>>	Date            : 2012-08-23
>>
>>Abstract:
>>   This document specifies a solution for the delivery of IPv4
>>multicast
>>   services to IPv4 clients over an IPv6 multicast network.  The
>>   solution relies upon a stateless IPv4-in-IPv6 encapsulation scheme
>>   and uses the IPv6 multicast distribution tree to deliver IPv4
>>   multicast traffic.  The solution is particularly useful for the
>>   delivery of multicast service offerings to DS-Lite serviced
>>   customers.
>>
>>
>>The IETF datatracker status page for this draft is:
>>https://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-multicast
>>
>>There's also a htmlized version available at:
>>http://tools.ietf.org/html/draft-ietf-softwire-dslite-multicast-03
>>
>>A diff from the previous version is available at:
>>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-softwire-dslite-mul
>>ticast-03
>>
>>
>>Internet-Drafts are also available by anonymous FTP at:
>>ftp://ftp.ietf.org/internet-drafts/
>>
>>_______________________________________________
>>Softwires mailing list
>>Softwires@ietf.org
>>https://www.ietf.org/mailman/listinfo/softwires
>>
>_______________________________________________
>Softwires mailing list
>Softwires@ietf.org
>https://www.ietf.org/mailman/listinfo/softwires

--B_3428584616_125724
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIVlwYJKoZIhvcNAQcCoIIViDCCFYQCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EzAwggUzMIIEG6ADAgECAhBTm5vcGTrcIPdnvVTe3rDkMA0GCSqGSIb3DQEBBQUAMIGTMQsw
CQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxm
b3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVu
dCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTEyMDIxNDAwMDAwMFoX
DTEzMDIxMzIzNTk1OVowKjEoMCYGCSqGSIb3DQEJARYZeWl1X2xlZUBjYWJsZS5jb21jYXN0
LmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANOm2q1Oat5U5a79IA1Yx+oa
djvccI4HQYLkQtDXj9an1bz7JT52yBADiZJ42pTJ35L4yPzYRY/4b1k7RCsodmRzu4F2n1wA
Xjg3hkRygwiAVrEv7p1FM4Wsr4nY6utC6/dhrJFkTtLzMmQXcSeVF1gpoaDKzf9UNvXNZCy8
dpLhdP4v8t7JOhfPyR3LBOo7vKk4WIv7ugGVgyLXwGSwu0rEVNOwLtPdoTJW0pi+ATaJeAuf
WVIKLRVjK56vKBeA3ms3BJNOp5zkfAk5j3IymZZMD156Tib5ViL8dCTycYZyMNWBOrDPC/yn
c4itE6q05Wh94QYGp6GcsZkiHEXFZrUCAwEAAaOCAekwggHlMB8GA1UdIwQYMBaAFHoTTgB0
W8Z4Y2QnwS/ioFu8ecV7MB0GA1UdDgQWBBTdz82GEvcyRLU/wx9KzuYvjgUddzAOBgNVHQ8B
Af8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQED
BQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYI
KwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMFcGA1UdHwRQME4wTKBK
oEiGRmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9u
YW5kU2VjdXJlRW1haWxDQS5jcmwwgYgGCCsGAQUFBwEBBHwwejBSBggrBgEFBQcwAoZGaHR0
cDovL2NydC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1
cmVFbWFpbENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuY29tb2RvY2EuY29tMCQG
A1UdEQQdMBuBGXlpdV9sZWVAY2FibGUuY29tY2FzdC5jb20wDQYJKoZIhvcNAQEFBQADggEB
AFeEfwmWgj/jpA3+ctSoBsbvHGnWLz00p8NBX2+qzz8QjgDpZT5T1Fux5MV6qlVJpND12pzq
ziUyFCBdv6QOMyiOrn5RxooXY9W6Hpa8qBD4v9BXy5qtP7gi4xJhFufXdNZXEw2RwNyjBzfV
/F2Q8HSwlyOwS+fHKYZZ9gy/KneVP//YcrC4icG1ipJQ2+gCUs+uUAouz0xF0uBYE/bQRTss
oRTY6D/X5lxarw28oocfr38v4Ro5bmsZlsEF22OvpKZX5tfz1aOL5U9nhXixY7Sd9B9BGHl7
mrybVUl7NnguWGIAhHiVD9ce1u4jJ1PnNmrNkvwJouS/7zYCId8000cwggUaMIIEAqADAgEC
AhBtGeqnGU9qMyLmIjJ6qnHeMA0GCSqGSIb3DQEBBQUAMIGuMQswCQYDVQQGEwJVUzELMAkG
A1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRS
VVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UE
AxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMB4XDTEx
MDQyODAwMDAwMFoXDTIwMDUzMDEwNDgzOFowgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJH
cmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD
QSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBT
ZWN1cmUgRW1haWwgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCShIRbS1eY
1F4vi6ThQMijU1hfZmXxMk73nzJ9VdB4TFW3QpTg+SdxB8XGaaS5MsTxQBqQzCdWYn8XtXFp
ruUgG+TLY15gyqJB9mrho/+43x9IbWVDjCouK2M4d9+xF6zC2oIC1tQyatRnbyATj1w1+uVU
gK/YcQodNwoCUFNslR2pEBS0mZVZEjH/CaLSTNxS297iQAFbSGjdxUq04O0kHzqvcV8H46y/
FDuwJXFoPfQP1hdYRhWBPGiLi4MPbXohV+Y0sNsyfuNK4aVScmQmkU6lkg//4LFg/RpvaFGZ
Y40ai6XMQpubfSJj06mg/M6ekN9EGfRcWzW6FvOnm//BAgMBAAGjggFLMIIBRzAfBgNVHSME
GDAWgBSJgmd9xJ0mcABLtFBIfN49rgRufTAdBgNVHQ4EFgQUehNOAHRbxnhjZCfBL+KgW7x5
xXswDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8CAQAwEQYDVR0gBAowCDAGBgRV
HSAAMFgGA1UdHwRRME8wTaBLoEmGR2h0dHA6Ly9jcmwudXNlcnRydXN0LmNvbS9VVE4tVVNF
UkZpcnN0LUNsaWVudEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMHQGCCsGAQUFBwEBBGgw
ZjA9BggrBgEFBQcwAoYxaHR0cDovL2NydC51c2VydHJ1c3QuY29tL1VUTkFkZFRydXN0Q2xp
ZW50X0NBLmNydDAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTANBgkq
hkiG9w0BAQUFAAOCAQEAhda+eFdVbTN/RFL+QtUGqAEDgIr7DbL9Sr/2r0FJ9RtaxdKtG3Nu
PukmfOZMmMEwKN/L+0I8oSU+CnXW0D05hmbRoZu1TZtvryhsHa/l6nRaqNqxwPF1ei+eupN5
yv7ikR5WdLL4jdPgQ3Ib7Y/9YDkgR/uLrzplSDyYPaUlv73vYOBJ5RbI6z9Dg/Dg7g3B080z
X5vQvWBqszv++tTJOjwf7Zv/m0kzvkIpOYPuM2kugp1FTahp2oAbHj3SGl18R5mlmwhtEpmG
1l1XBxunML5LSUS4kH7K0Xk467Qz+qA6XSZYnmFVGLQh1ZnV4ENAQjC+6qXnlNKw/vN1+X9u
5zCCBJ0wggOFoAMCAQICEDQ96SusJzT/j8s0lPvMcFQwDQYJKoZIhvcNAQEFBQAwbzELMAkG
A1UEBhMCU0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRl
cm5hbCBUVFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAe
Fw0wNTA2MDcwODA5MTBaFw0yMDA1MzAxMDQ4MzhaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UE
CBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNU
IE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMt
VVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxq
mNVNNRm5pELlzkniii8efNIxB8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPM
yaQylbsMTzC9mKALi+VuG6JG+ni8om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbN
oKXqvgvOdjp6Dpvq/NonWz1zHyLmSGHGTPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcR
Wdq6hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7NlyP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/
MLbu9mIwFIws6wIDAQABo4H0MIHxMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1Qa
MB0GA1UdDgQWBBSJgmd9xJ0mcABLtFBIfN49rgRufTAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0T
AQH/BAUwAwEB/zARBgNVHSAECjAIMAYGBFUdIAAwRAYDVR0fBD0wOzA5oDegNYYzaHR0cDov
L2NybC51c2VydHJ1c3QuY29tL0FkZFRydXN0RXh0ZXJuYWxDQVJvb3QuY3JsMDUGCCsGAQUF
BwEBBCkwJzAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTANBgkqhkiG
9w0BAQUFAAOCAQEAAbyc42MosPMxAcLfe91ioAGdIzEPnJJzU1HqH0z61p/Eyi9nfngzD3QW
uZGHkfWKJvpkcADYHvkLBGJQh5OB1Nr1I9s0u4VWtHA0bniDNx6FHMURFZJfhxe9rGr98cLR
zIlfsXzwPlHyNfN87GCYazor4O/fs32G67Ub9VvsonyYE9cAULnRLXPeA3h04QWFMV7Lmrmd
lMa5lDd1ctxE+2fo8PolHlKn2iXpR+CgxzygTrEKNvt3SJ/vl4r7tP7jlBSog7xcLT/SYHFg
7sJxggzpiDbj2iC0o6BsqpZLuICOdcpJB/Y7FLrf3AXZn9vgsuZNoHgm5+ctbn9fxh6IFTCC
BDYwggMeoAMCAQICAQEwDQYJKoZIhvcNAQEFBQAwbzELMAkGA1UEBhMCU0UxFDASBgNVBAoT
C0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBUVFAgTmV0d29yazEi
MCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAeFw0wMDA1MzAxMDQ4MzhaFw0y
MDA1MzAxMDQ4MzhaMG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQG
A1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0
IEV4dGVybmFsIENBIFJvb3QwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC39xoz
5vIABC054E5b7R+8bA/Ntfojts7emxEzl6QpTH2Tn71KvJPtAxrjj8/lbVBa1pcplFqAsEl6
2y6V/bjKvzc4LR4+kUGtcFbH8E8/6DKedMrIkFTpxl8PeJ2aQDwOrGGqXhSPnoehalDc15pO
rwWzpnGUnHGzUGAKxxOdOAeGAqjpqGkmGJCrTLBPI6s6T4TY386f4Wlvu9dC12tE5Met7m1B
X3JacQg3s3llpFmglDf3AC8NwpJy2tA4ctsUqEXEXSp9t7TWxO6szRNEt8kr3UMAJfphuWlq
WCMRt6czj1Z1WfXNKddGtworZbbTQm8Vsrh7++/pXVPVNFonAgMBAAGjgdwwgdkwHQYDVR0O
BBYEFK29mHo0tCb3+sQmVO8DveAky1QaMAsGA1UdDwQEAwIBBjAPBgNVHRMBAf8EBTADAQH/
MIGZBgNVHSMEgZEwgY6AFK29mHo0tCb3+sQmVO8DveAky1QaoXOkcTBvMQswCQYDVQQGEwJT
RTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAkBgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRU
UCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVzdCBFeHRlcm5hbCBDQSBSb290ggEBMA0GCSqG
SIb3DQEBBQUAA4IBAQCwm+CFJcLWI+IPlgaSnUGYnNmEeYHZHlsUByM2ZY+w2He7rEFsR2CD
UbD5Mj3n/PYmE8eAFqW/WvyHz3h5iSGa4kwHCoY1vPLeUcTSlrfcfk7ucP0cOesMAlEULY69
FuDB30Z15ySt7PRCtIWTcBBnup0GNUoY0yt6zFFCoXpj0ea7ocUrwja+Ew3mvWN+eXunCQ1A
q2rdj4rD9vaMGkIFUdRF9Z+nYiFoFSBDPJnnfL0k2KmRF3OIP1YbMTgYtHEPms3IDp6OLhvh
jJiDyx8x8URMxgRzSXZgD8f4vReAay7pzEwOWpp5DyAKLtWeYyYeVZKU2IIXWnvQvMePToYE
MYICLzCCAisCAQEwgagwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNo
ZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkw
NwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwg
Q0ECEFObm9wZOtwg92e9VN7esOQwCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJBDEWBBQ/QV3D
eq9ZLyqTSq9YhKGnC8bOIDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ
BTEPFw0xMjA4MjMyMDM2NTVaMA0GCSqGSIb3DQEBAQUABIIBAKr/zBFP5PsUbsATwcYKnPfM
u4v5ewLVBfpVRwI0hXlda4uwQlIB3SnUImbDu4xWPtqQbh34pmd0eEUjK6tYRu9IS6jHVo90
0W1xCIBDlbMeUtMNuONU26WZC77BWcCn1AJVngbElv3zOSgOn6ry7HrSAyo63GK32memtnts
aYgKS54SJiqrVO+0OP0x7DIf9xDmvuTvY7BxebVI1DHnl4p6vfZzjOgIWx3ERIDW3BGqZmDt
NMmZzT9778aEqIXKGCFW9hTD1K28dMR5l7T+lpu0+MkTNu1vn36+j9jvxQnbSTdn5vDPNjeL
dqgemYPWmVAtEq84pE84EQUULyevyd4=

--B_3428584616_125724--

From internet-drafts@ietf.org  Thu Aug 23 23:10:10 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4810C21F8540; Thu, 23 Aug 2012 23:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eW3nDvcTZfMG; Thu, 23 Aug 2012 23:10:09 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B142921F853D; Thu, 23 Aug 2012 23:10:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20120824061009.9050.41652.idtracker@ietfa.amsl.com>
Date: Thu, 23 Aug 2012 23:10:09 -0700
Cc: mboned@ietf.org
Subject: [MBONED] I-D Action: draft-ietf-mboned-64-multicast-address-format-04.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2012 06:10:10 -0000

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 IET=
F.

	Title           : IPv6 Multicast Address With Embedded IPv4 Multicast Addr=
ess
	Author(s)       : Mohamed Boucadair
                          Jacni Qin
                          Yiu L. Lee
                          Stig Venaas
                          Xing Li
                          Mingwei Xu
	Filename        : draft-ietf-mboned-64-multicast-address-format-04.txt
	Pages           : 13
	Date            : 2012-08-23

Abstract:
   This document reserves one bit of the unicast prefix-based multicast
   IPv6 address for ASM and an IPv6 multicast prefix for SSM mode to be
   used in the context of IPv4-IPv6 interconnection.  The document
   specifies an algorithmic translation of an IPv6 multicast address to
   a corresponding IPv4 multicast address, and vice versa.  This
   algorithmic translation can be used in both IPv4-IPv6 translation or
   encapsulation schemes.

   This document updates RFC 3306.  One of the reserved bits defined in
   RFC 3306 has now a meaning.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast-address-for=
mat

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mboned-64-multicast-address-f=
ormat-04


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


From mohamed.boucadair@orange.com  Fri Aug 24 01:37:50 2012
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26BAA21F8516 for <mboned@ietfa.amsl.com>; Fri, 24 Aug 2012 01:37:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.063
X-Spam-Level: 
X-Spam-Status: No, score=-2.063 tagged_above=-999 required=5 tests=[AWL=0.185,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pmj-DYyLjDMm for <mboned@ietfa.amsl.com>; Fri, 24 Aug 2012 01:37:49 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id A77B821F8513 for <mboned@ietf.org>; Fri, 24 Aug 2012 01:37:46 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 618EB22CF64 for <mboned@ietf.org>; Fri, 24 Aug 2012 10:37:45 +0200 (CEST)
Received: from PUEXCH51.nanterre.francetelecom.fr (unknown [10.101.44.31]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 4A8D4238048 for <mboned@ietf.org>; Fri, 24 Aug 2012 10:37:45 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH51.nanterre.francetelecom.fr ([10.101.44.31]) with mapi; Fri, 24 Aug 2012 10:37:23 +0200
From: <mohamed.boucadair@orange.com>
To: "mboned@ietf.org" <mboned@ietf.org>
Date: Fri, 24 Aug 2012 10:37:22 +0200
Thread-Topic: draft-ietf-mboned-64-multicast-address-format-04
Thread-Index: Ac2Bvx34WZhjxOX/SJi7q0CM1MERfQAEhuRw
Message-ID: <94C682931C08B048B7A8645303FDC9F36E5332A9B2@PUEXCB1B.nanterre.francetelecom.fr>
References: <20120824061009.9050.41652.idtracker@ietfa.amsl.com>
In-Reply-To: <20120824061009.9050.41652.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.8.24.60412
Subject: [MBONED] draft-ietf-mboned-64-multicast-address-format-04
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2012 08:37:50 -0000

Dear all,

We submitted a new version of the draft to take into account the comments r=
eceived so far.=20
The main changes are as follows:

   o  Indicate the draft update RFC3306 as suggested by T. Chown.  We
      didn't added a note about rfc3956 as we are defining a bit
      reserved in 3306.

   o  Because of the previous comment, the wording has been changed to
      indicate we are reserving a bit in the unicast prefix-based
      address not reserving a prefix for ASM.  The rationale behind that
      is to encourage implementations check the value of the
      reserved bit rather than matching a prefix.

   o  Clarify the meaning of "x" as requested by Behcet.

   o  Behcet asked to reserve a /17 or /12 for ASM.  We didn't considered
      that comment because we received in the past comments arguing that
      reserving /17 is a waste of multicast address space.  This is
      documented in Section 3.1 of the draft.

   o  Implemented some wording changes suggested by P. Koch.

   o  Update the section with examples.


A detailed diff is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-i=
etf-mboned-64-multicast-address-format-04.


If you still have a concern with the new version, please discuss it in the =
list.

Cheers,
Med




From internet-drafts@ietf.org  Fri Aug 24 05:44:46 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08EE221F86C2; Fri, 24 Aug 2012 05:44:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1dzZgtUp2xFv; Fri, 24 Aug 2012 05:44:45 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87DC621F854B; Fri, 24 Aug 2012 05:44:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20120824124445.7604.96581.idtracker@ietfa.amsl.com>
Date: Fri, 24 Aug 2012 05:44:45 -0700
Cc: mboned@ietf.org
Subject: [MBONED] I-D Action: draft-ietf-mboned-64-multicast-address-format-04.txt
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2012 12:44:46 -0000

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 IET=
F.

	Title           : IPv6 Multicast Address With Embedded IPv4 Multicast Addr=
ess
	Author(s)       : Mohamed Boucadair
                          Jacni Qin
                          Yiu L. Lee
                          Stig Venaas
                          Xing Li
                          Mingwei Xu
	Filename        : draft-ietf-mboned-64-multicast-address-format-04.txt
	Pages           : 13
	Date            : 2012-08-23

Abstract:
   This document reserves one bit of the unicast prefix-based multicast
   IPv6 address for ASM and an IPv6 multicast prefix for SSM mode to be
   used in the context of IPv4-IPv6 interconnection.  The document
   specifies an algorithmic translation of an IPv6 multicast address to
   a corresponding IPv4 multicast address, and vice versa.  This
   algorithmic translation can be used in both IPv4-IPv6 translation or
   encapsulation schemes.

   This document updates RFC 3306.  One of the reserved bits defined in
   RFC 3306 has now a meaning.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast-address-for=
mat

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mboned-64-multicast-address-format-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mboned-64-multicast-address-f=
ormat-04


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


From stig@venaas.com  Fri Aug 24 15:40:26 2012
Return-Path: <stig@venaas.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F8E121F8576 for <mboned@ietfa.amsl.com>; Fri, 24 Aug 2012 15:40:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.523
X-Spam-Level: 
X-Spam-Status: No, score=-102.523 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yyAfgdKTDWzw for <mboned@ietfa.amsl.com>; Fri, 24 Aug 2012 15:40:26 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id ECD1C21F8554 for <mboned@ietf.org>; Fri, 24 Aug 2012 15:40:25 -0700 (PDT)
Received: from [IPv6:2001:420:301:1004:2813:da6:1dff:7b0f] (unknown [IPv6:2001:420:301:1004:2813:da6:1dff:7b0f]) by ufisa.uninett.no (Postfix) with ESMTPSA id 635557FEF; Sat, 25 Aug 2012 00:40:24 +0200 (CEST)
Message-ID: <503802D6.5040409@venaas.com>
Date: Fri, 24 Aug 2012 15:40:22 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
References: <mailman.584.1343157655.3364.mboned@ietf.org> <13205C286662DE4387D9AF3AC30EF456D770C81AE2@EMBX01-WF.jnpr.net> <50103032.9060900@venaas.com> <13205C286662DE4387D9AF3AC30EF456D770C8209C@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D770C8209C@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] recharter text
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2012 22:40:26 -0000

On 7/25/2012 11:35 AM, Ronald Bonica wrote:
>
>>
>> - Analyze the need for IPv4 - IPv6 multicast transition solutions
>>
>
> Stig,
>
> I would be happy with this text, but nothing more. AFAIKS, an thorough analysis of the need for IPv4 - IPv6 multicast transition solutions may reveal that:
>
> - there is an need to solve the IPvX-DualStack-IPvY use cases
> - all other use cases are best addressed by caching content on strategically located, dual-stack devices or, even better, by deploying dual stack
>
> If we were to put anything about MLTRANS solutions into the document, we might be committing to do work that will never see deployment.

Sure. Sorry for the late reply. I think we're in agreement then. I'm
just saying that we should at least have text describing the work the
WG already has taken on (the two adopted drafts). I think adding that
one sentence should be sufficient.

We don't know yet whether the WG should do more work...

Stig

>                                                       Ron
>


From sarikaya2012@gmail.com  Thu Aug 30 11:39:00 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F6AA21F85C4 for <mboned@ietfa.amsl.com>; Thu, 30 Aug 2012 11:39:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.105
X-Spam-Level: 
X-Spam-Status: No, score=-3.105 tagged_above=-999 required=5 tests=[AWL=-0.506, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3wuje1xeCp97 for <mboned@ietfa.amsl.com>; Thu, 30 Aug 2012 11:38:59 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8151021F85A8 for <mboned@ietf.org>; Thu, 30 Aug 2012 11:38:57 -0700 (PDT)
Received: by ieak13 with SMTP id k13so1178430iea.31 for <mboned@ietf.org>; Thu, 30 Aug 2012 11:38:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=NIlqRJB4XQuT6qwn/Wy1WVd3aNuHDHgEa0YzMWNhppU=; b=XyLhGxQPQkhwvlYNq7Z2isUHICYrECjGvwgcT+tNXMqllM/yUJxTP+9Pr5ctkJszLZ ZJU7bWLcsBR0TM2vLrOPh/tKSxbqTBrOTgjDCNjk7QWPYzm2WGDi4sRr1hnSbCe2T/VJ k6RWQIYPvjalHNcO7nQnVCwJrtMe38+c9AGXDeDrtVHssGHlQ1ImII6Jym9Gc9VoCkwp 0vzHY2OcogYbG49g/30uDKVC3bomwTDboafkz1VBsRSGuFg7jnHJt3UA+vBw44Q4RCkq kKdLLGu2GxNsvb0lHvFGXv0ViwT+MIABVEy4sUVRtbY3XJevZv5ui7uu/FowNuqy/NFp crgQ==
MIME-Version: 1.0
Received: by 10.42.18.193 with SMTP id y1mr5931893ica.0.1346351936732; Thu, 30 Aug 2012 11:38:56 -0700 (PDT)
Received: by 10.231.55.70 with HTTP; Thu, 30 Aug 2012 11:38:56 -0700 (PDT)
In-Reply-To: <E3FAB1F4F41F3A45B287E8D9C53522FD379E57CD@PACDCEXMB05.cable.comcast.com>
References: <94C682931C08B048B7A8645303FDC9F36E5332A8E5@PUEXCB1B.nanterre.francetelecom.fr> <E3FAB1F4F41F3A45B287E8D9C53522FD379E57CD@PACDCEXMB05.cable.comcast.com>
Date: Thu, 30 Aug 2012 13:38:56 -0500
Message-ID: <CAC8QAce=NQN-KNwmqKbALrt4aSvatf59UoT-=iUO-r8iewzSxQ@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "mboned@ietf.org" <mboned@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [MBONED] FW: [Softwires] draft-ietf-softwire-dslite-multicast-03
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mboned>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Aug 2012 18:39:00 -0000

I think it is better to ask for adoption because this draft is a
solution draft for mboned problem statement draft,
draft-ietf-mboned-v4v6-mcast-ps.

Regards,

Behcet
On Thu, Aug 23, 2012 at 3:36 PM, Lee, Yiu <Yiu_Lee@cable.comcast.com> wrote=
:
> Hi,
>
> We submitted a revision of softwire-dslite-multicast to WGLC. This draft
> would use the mboned-64-multicast-address-format. We would like this WG t=
o
> review this draft and give us feedback.
>
> Thanks,
> Yiu
>
>
> On 8/23/12 10:54 AM, "mohamed.boucadair@orange.com"
> <mohamed.boucadair@orange.com> wrote:
>
>>Dear all,
>>
>>A new version taking into account comments received during the WGLC has
>>been submitted. The main changes are:
>>
>>* change the title
>>* clarify the solution is generic for any 4-6-4 use case and the solution
>>has been designed with DS-Lite in mind
>>* add a discussion about scoping: preserve the scope when translation
>>multicast addresses
>>* add a note only IPv4-in-IPv6 encap is detailed in the document but
>>other tunnelling techniques may be defined in the future
>>* update the security section with some discussions related to scoping.
>>* + other editorial changes.
>>
>>To view the detailed changes:
>>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-softwire-dslite-multicast-0=
3
>>
>>I hope this version solve the concerns raised during the WGLC.
>>
>>Cheers,
>>Med
>>
>>
>>>-----Message d'origine-----
>>>De : softwires-bounces@ietf.org
>>>[mailto:softwires-bounces@ietf.org] De la part de
>>>internet-drafts@ietf.org
>>>Envoy=E9 : jeudi 23 ao=FBt 2012 16:47
>>>=C0 : i-d-announce@ietf.org
>>>Cc : softwires@ietf.org
>>>Objet : [Softwires] I-D Action:
>>>draft-ietf-softwire-dslite-multicast-03.txt
>>>
>>>
>>>A New Internet-Draft is available from the on-line
>>>Internet-Drafts directories.
>>> This draft is a work item of the Softwires Working Group of the IETF.
>>>
>>>      Title           : Delivery of IPv4 Multicast Services
>>>to IPv4 Clients over an IPv6 Multicast Network
>>>      Author(s)       : Jacni Qin
>>>                          Mohamed Boucadair
>>>                          Christian Jacquenet
>>>                          Yiu L. Lee
>>>                          Qian Wang
>>>      Filename        : draft-ietf-softwire-dslite-multicast-03.txt
>>>      Pages           : 20
>>>      Date            : 2012-08-23
>>>
>>>Abstract:
>>>   This document specifies a solution for the delivery of IPv4
>>>multicast
>>>   services to IPv4 clients over an IPv6 multicast network.  The
>>>   solution relies upon a stateless IPv4-in-IPv6 encapsulation scheme
>>>   and uses the IPv6 multicast distribution tree to deliver IPv4
>>>   multicast traffic.  The solution is particularly useful for the
>>>   delivery of multicast service offerings to DS-Lite serviced
>>>   customers.
>>>
>>>
>>>The IETF datatracker status page for this draft is:
>>>https://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-multicast
>>>
>>>There's also a htmlized version available at:
>>>http://tools.ietf.org/html/draft-ietf-softwire-dslite-multicast-03
>>>
>>>A diff from the previous version is available at:
>>>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-softwire-dslite-mul
>>>ticast-03
>>>
>>>
>>>Internet-Drafts are also available by anonymous FTP at:
>>>ftp://ftp.ietf.org/internet-drafts/
>>>
>>>_______________________________________________
>>>Softwires mailing list
>>>Softwires@ietf.org
>>>https://www.ietf.org/mailman/listinfo/softwires
>>>
>>_______________________________________________
>>Softwires mailing list
>>Softwires@ietf.org
>>https://www.ietf.org/mailman/listinfo/softwires
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>
