
From lenny@juniper.net  Tue May  1 09:22:42 2012
Return-Path: <lenny@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 3894421E81A5 for <mboned@ietfa.amsl.com>; Tue,  1 May 2012 09:22:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 HFEohy6rFr+i for <mboned@ietfa.amsl.com>; Tue,  1 May 2012 09:22:41 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 539F921E80A2 for <mboned@ietf.org>; Tue,  1 May 2012 09:22:41 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKT6AN0HUQ+UX1V3YhTWWFXqZfmNv+q5It@postini.com; Tue, 01 May 2012 09:22:41 PDT
Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB02-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 1 May 2012 09:21:30 -0700
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id q41GLQ195287	for <mboned@ietf.org>; Tue, 1 May 2012 09:21:28 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 4BC3D11489;  Tue,  1 May 2012 09:21:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id 412851144F	for <mboned@ietf.org>; Tue,  1 May 2012 09:21:26 -0700 (PDT)
Date: Tue, 1 May 2012 09:21:26 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: MBONED WG <mboned@ietf.org>
In-Reply-To: <20120419153427.X31500@eng-mail01.juniper.net>
Message-ID: <20120501091813.D33698@eng-mail01.juniper.net>
References: <mailman.2854.1334523092.3230.mboned@ietf.org> <13205C286662DE4387D9AF3AC30EF456D76A760955@EMBX01-WF.jnpr.net> <20120419153427.X31500@eng-mail01.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Subject: Re: [MBONED] draft-jaclee as WG document?
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, 01 May 2012 16:22:42 -0000

There appears to be consensus to adopt draft-jaclee-behave-v4v6-mcast-ps 
as a WG doc in MBONED.

Authors- please resubmit with appropriate draft-ietf-... name.


On Thu, 19 Apr 2012, Leonard Giuliano wrote:

-) 
-) The authors of both drafts have agreed that 
-) draft-eubanks-mboned-transition-overview will be abandoned and 
-) draft-jaclee-behave-v4v6-mcast-ps will the basis for further work in 
-) multicast transition.
-) 
-) Please speak up in support of/opposition to adopting 
-) draft-jaclee-behave-v4v6-mcast-ps as an MBONED document by Fri, April 27.  
-) 
-) The 10 folks who have already responded to Tom's original email need not 
-) reply again- you're support is noted.
-) 
-) 
-) 
-) 
-) On Thu, 19 Apr 2012, Ronald Bonica wrote:
-) 
-) -) Tom,
-) -) 
-) -) The next step in the process is for the chairs to post a question to the WG asking whether this draft should be adopted as a WG item. An important part of that message is a cut-off date for responses. Without that, we have no idea how long we should wait before expecting a consensus call.
-) -) 
-) -) I have asked the chairs to post this message.
-) -) 
-) -)                                           Ron
-) -) 
-) -) > 
-) -) > Message: 1
-) -) > Date: Sun, 15 Apr 2012 16:51:23 -0400
-) -) > From: Tom Taylor <tom.taylor.stds@gmail.com>
-) -) > To: MBONED WG <mboned@ietf.org>
-) -) > Subject: [MBONED] draft-jaclee as WG document?
-) -) > Message-ID: <4F8B34CB.1060306@gmail.com>
-) -) > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
-) -) > 
-) -) > At the meeting, there was solid support for using draft-jaclee-behave-
-) -) > v4v6-mcast-ps as the basis for further work in multicast transition. In
-) -) > addition, the agreed wording of the charter at the beginning of the
-) -) > meeting included coverage of the topic:
-) -) > 
-) -) > "Develop requirements for tools that assist in multicast ... transition
-) -) > ..."
-) -) > 
-) -) > In view of these findings, will the Chairs consider making draft-jaclee
-) -) > an Mboned Workiong Group document?
-) -) > 
-) -) > Tom Taylor
-) -) > 
-) -) > 
-) -) > ------------------------------
-) -) > 
-) -) 
-) -) _______________________________________________
-) -) MBONED mailing list
-) -) MBONED@ietf.org
-) -) https://www.ietf.org/mailman/listinfo/mboned
-) -) 
-) 

From Tina.Tsou.Zouting@huawei.com  Wed May  2 11:59:14 2012
Return-Path: <Tina.Tsou.Zouting@huawei.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 6F67E21F84D0 for <mboned@ietfa.amsl.com>; Wed,  2 May 2012 11:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.452
X-Spam-Level: 
X-Spam-Status: No, score=-2.452 tagged_above=-999 required=5 tests=[AWL=0.146,  BAYES_00=-2.599, HTML_MESSAGE=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 Oxd5+7Kfm8cm for <mboned@ietfa.amsl.com>; Wed,  2 May 2012 11:59:14 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id D0A6F21F84CF for <mboned@ietf.org>; Wed,  2 May 2012 11:59:13 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFT73979; Wed, 02 May 2012 14:59:13 -0400 (EDT)
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 2 May 2012 11:57:36 -0700
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by dfweml405-hub.china.huawei.com (10.193.5.102) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 2 May 2012 11:57:40 -0700
Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.48]) by szxeml411-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Thu, 3 May 2012 02:57:34 +0800
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: draft-tsou-mboned-multrans-addr-acquisition-01
Thread-Index: Ac0olW4tpAJfzZWwTw2lKRKI4vlTgA==
Date: Wed, 2 May 2012 18:57:34 +0000
Message-ID: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.193.34.105]
Content-Type: multipart/alternative; boundary="_000_C0E0A32284495243BDE0AC8A066631A80C9B185Eszxeml526mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 02 May 2012 18:59:14 -0000

--_000_C0E0A32284495243BDE0AC8A066631A80C9B185Eszxeml526mbschi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Now that the multicast transition framework document is officially accepted=
, is the Working Group prepared also to take on the topic of address acquis=
ition, which is one of the tasks it identifies?
If so, would draft-tsou-mboned-multrans-addr-acquisition-01 be acceptable a=
s a starting point?

Tina


--_000_C0E0A32284495243BDE0AC8A066631A80C9B185Eszxeml526mbschi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Now that the multicast transition framework docum=
ent is officially accepted, is the Working Group prepared also to take on t=
he topic of address acquisition, which is one of the tasks it identifies?<o=
:p></o:p></p>
<p class=3D"MsoNormal">If so, would draft-tsou-mboned-multrans-addr-acquisi=
tion-01 be acceptable as a starting point?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Tina<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_C0E0A32284495243BDE0AC8A066631A80C9B185Eszxeml526mbschi_--

From cabo@tzi.org  Sun May  6 13:57:52 2012
Return-Path: <cabo@tzi.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 B735A21F84F0; Sun,  6 May 2012 13:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.287
X-Spam-Level: 
X-Spam-Status: No, score=-106.287 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 FaWMSzbt2TOr; Sun,  6 May 2012 13:57:51 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 890AA21F84AA; Sun,  6 May 2012 13:57:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q46KvdU6003700; Sun, 6 May 2012 22:57:39 +0200 (CEST)
Received: from [192.168.217.105] (p548996D9.dip.t-dialin.net [84.137.150.217]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id F1E4B111; Sun,  6 May 2012 22:57:38 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1257)
From: Carsten Bormann <cabo@tzi.org>
Date: Sun, 6 May 2012 22:57:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <92309DC0-A179-4B5B-9D8C-4B55F64A4668@tzi.org>
To: draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>
X-Mailer: Apple Mail (2.1257)
X-Mailman-Approved-At: Sun, 06 May 2012 21:26:23 -0700
Cc: mboned@ietf.org, 6man@ietf.org, The IESG <iesg@ietf.org>
Subject: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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: Sun, 06 May 2012 20:57:52 -0000

I have been selected as the Applications Area Directorate reviewer for
this draft (for background on appsdir, please see
=
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate
).

Please resolve these comments along with any other Last Call comments
you may receive. Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Gr=FC=DFe, Carsten
---------------------------------

Document: draft-ietf-mboned-64-multicast-address-format-01
Title: IPv4-Embedded IPv6 Multicast Address Format
Reviewer: Carsten Bormann
Review Date: 2012-05-06
IETF Last Call Date: 2012-04-19

** Summary: This draft is NOT ready for publication as a Proposed
Standard and should be revised before publication.

The document appears as an attempt to extend the reasoning of RFC 6052
to multicast IPv4 addresses.  However, while unicast IPv4 addresses
and their IPv6 counterparts are assigned as part of network
configuration, multicast addresses are decided upon by applications.
The document is very short on information how an application should
decide when to make use of the newly defined formats.  It is therefore
also hard to understand why these formats are needed in the first
place.  There appears to be a transition model in the minds of the
authors that makes this necessary or practical, and this information
must be made part of the document for it to be useful.

** Major Issues:

To continue the summary: I don't understand which network elements
need to be able to determine, by looking at an IP address, that this
document is in use.  What for?  More generally, which entities need to
interoperate based on a common understanding of this format?

Of the various fields left "configurable according to local policies
of the entity managing the IPv4-IPv6 Interconnection Function", which
are important for applications?  How do they know these policies?  If
that information is all in the two parameters "ASM_MPREFIX64" and
"SSM_MPREFIX64", what is the protocol that will be used to make this
information available to applications?  I don't think this can be a
standards-track document without defining at least one MTI protocol
for disseminating this information.  What is an implementation
supposed to do that receives an address that looks like it is governed
by this document but does not conform to either of the agreed
prefixes disseminated to the implementation?

This document needs editorial attention.  I will abstain from trying
to make detailed corrections, as this would become tedious quickly.
While much of this work could be done by the RFC editor, some of the
editorial decisions will enter e.g. IANA registries, so the technical
terms need to be decided now.  More importantly, understanding this
document during its development process (including mine as a reviewer)
may be hampered by its editorial shortcomings.

** Minor Issues:

My first editorial problem is with the title.  This address format is
not embedded in IPv4, as the title wants to make us believe.  Instead,
it is talking about an multicast address format for IPv6 that embeds
an IPv4 multicast address.  (While this misleading naming repeats the
same mistake that has been made in RFC 6052, at least there it is not
part of the title.)

3

The role of 64IX is very unclear.  My conjecture is that this draft is
defining the address format for the case M=3D1 only (i.e., address[16] =3D=

1).  No text defines what happens for M=3D0, so the assumption appears
to be that RFC 4291 applies unchanged in this case.  If this
conjecture is correct, this needs to be made much clearer.

What is "r"?  Define.

4

Why is 64IX moving around here?
(The discriminating bit M now seems to be address[32].)
How does one find out which of the two positions of the M bit to use?

.          o  sub-group-id: The default value is all zeros.
How does an application find out when to choose a different one?

.             232.0.0.1-232.0.0.255 range is being
.             reserved to IANA.
Who is making this reservation?  ("is being reserved" means the
resernation is going on right now, but I don't find anything in 9.)

7

7 seems to imply this format is only useful where RFC 6052 is in use.
If this is true, this should be clearly stated.  More specifically,
the assumption appears to be that all nodes that need to exchange
information that concerns IPv4 sources need to have the same RFC 6052
parameters in effect.  How is that ensured?

** Nits:

10 -- s/defined/defines/

(And many more, see above.)


From mohamed.boucadair@orange.com  Wed May  9 06:09:32 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 3B63721F858E; Wed,  9 May 2012 06:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.089
X-Spam-Level: 
X-Spam-Status: No, score=-2.089 tagged_above=-999 required=5 tests=[AWL=0.159,  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 qGfRz4mzDl+l; Wed,  9 May 2012 06:09:31 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id EBFFD21F8532; Wed,  9 May 2012 06:09:27 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 5591622C78E; Wed,  9 May 2012 15:09:27 +0200 (CEST)
Received: from puexch31.nanterre.francetelecom.fr (unknown [10.101.44.29]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 37E1935C05A; Wed,  9 May 2012 15:09:27 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.233.200.25]) by puexch31.nanterre.francetelecom.fr ([10.101.44.29]) with mapi; Wed, 9 May 2012 15:09:26 +0200
From: <mohamed.boucadair@orange.com>
To: Carsten Bormann <cabo@tzi.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>
Date: Wed, 9 May 2012 15:09:25 +0200
Thread-Topic: APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
Thread-Index: Ac0ryvGBItecPVlyRGu344fhCanxhwCEpA8A
Message-ID: <94C682931C08B048B7A8645303FDC9F36E29946F71@PUEXCB1B.nanterre.francetelecom.fr>
References: <92309DC0-A179-4B5B-9D8C-4B55F64A4668@tzi.org>
In-Reply-To: <92309DC0-A179-4B5B-9D8C-4B55F64A4668@tzi.org>
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.5.9.121229
Cc: "mboned@ietf.org" <mboned@ietf.org>, "6man@ietf.org" <6man@ietf.org>, The IESG <iesg@ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 09 May 2012 13:09:32 -0000

Dear Carsten,

Thank you for the review.=20

Please see inline.

Cheers,
Med=20

>-----Message d'origine-----
>De : Carsten Bormann [mailto:cabo@tzi.org]=20
>Envoy=E9 : dimanche 6 mai 2012 22:58
>=C0 :=20
>draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.or
>g; apps-discuss@ietf.org application-layer protocols
>Cc : The IESG; 6man@ietf.org; mboned@ietf.org
>Objet : APPSDIR review of=20
>draft-ietf-mboned-64-multicast-address-format-01
>
>I have been selected as the Applications Area Directorate reviewer for
>this draft (for background on appsdir, please see
>http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaD
>irectorate
>).
>
>Please resolve these comments along with any other Last Call comments
>you may receive. Please wait for direction from your document shepherd
>or AD before posting a new version of the draft.
>
>Gr=FC=DFe, Carsten
>---------------------------------
>
>Document: draft-ietf-mboned-64-multicast-address-format-01
>Title: IPv4-Embedded IPv6 Multicast Address Format
>Reviewer: Carsten Bormann
>Review Date: 2012-05-06
>IETF Last Call Date: 2012-04-19
>
>** Summary: This draft is NOT ready for publication as a Proposed
>Standard and should be revised before publication.
>
>The document appears as an attempt to extend the reasoning of RFC 6052
>to multicast IPv4 addresses.  However, while unicast IPv4 addresses
>and their IPv6 counterparts are assigned as part of network
>configuration, multicast addresses are decided upon by applications.
>The document is very short on information how an application should
>decide when to make use of the newly defined formats.  It is therefore
>also hard to understand why these formats are needed in the first
>place.  There appears to be a transition model in the minds of the
>authors that makes this necessary or practical, and this information
>must be made part of the document for it to be useful.

Med: There are plenty of applications using this address format: e.g., [I-D=
.ietf-softwire-mesh-multicast], [I-D.ietf-softwire-dslite-multicast], [I-D.=
ietf-softwire-multicast-prefix-option], [I-D.venaas-behave-v4v6mc-framework=
],  [I-D.sarikaya-behave-netext-nat64-pmip], [I-D.sarikaya-behave-mext-nat6=
4-dsmip], etc. We had pointers to some of those drafts in earlier versions =
of the document but we removed them and adopted the same approach as RFC605=
2: only the address format is defined while the usage is defined in compani=
on documents. More details are also documented here: http://tools.ietf.org/=
html/draft-boucadair-behave-64-multicast-address-format-03#appendix-A.1 and=
 http://tools.ietf.org/html/draft-boucadair-behave-64-multicast-address-for=
mat-03#appendix-A.2.=20

There is also a problem statement, available at: http://tools.ietf.org/html=
/draft-jaclee-behave-v4v6-mcast-ps-03 which can be cited in the introductio=
n.=20

>
>** Major Issues:
>
>To continue the summary: I don't understand which network elements
>need to be able to determine, by looking at an IP address, that this
>document is in use.  What for?  More generally, which entities need to
>interoperate based on a common understanding of this format?

Med: Elements which make use of the address format are deployment-specific;=
 this can be a receiver, an IPv4-IPv6 PIM interworking function, IGMP/MLD I=
nterworking function. We didn't quoted these interworking functions because=
 this is deployment-specific. Do you think your issue can be solved if we a=
dd a pointer to one of the solutions documented listed above? =20

>
>Of the various fields left "configurable according to local policies
>of the entity managing the IPv4-IPv6 Interconnection Function", which
>are important for applications?  How do they know these policies?

Med: The content of this filed is left configurable. Its value will depend =
on the policies enforced by the administrative entity. Examples of these po=
licies are: embedded-RF, use unicast-based prefix, etc. Applications are no=
t aware of these policies since a prefix will (likely /96) will be provisio=
ned (see Section 6).

  If
>that information is all in the two parameters "ASM_MPREFIX64" and
>"SSM_MPREFIX64", what is the protocol that will be used to make this
>information available to applications?  I don't think this can be a
>standards-track document without defining at least one MTI protocol
>for disseminating this information.

Med: The provisioning of the ASM_PREFIX64 and the SSM_PREFIX is orthogonal =
to the address format itself. Various methods can be used but this is out o=
f scope of the document. We can add a pointer to http://tools.ietf.org/html=
/draft-ietf-softwire-multicast-prefix-option-00 as a provisioning example. =
Would you be fine with adding such reference?


  What is an implementation
>supposed to do that receives an address that looks like it is governed
>by this document but does not conform to either of the agreed
>prefixes disseminated to the implementation?

Med: This is an issue for the provisioning method and not for the specifica=
tion of the address format itself.

>
>This document needs editorial attention.  I will abstain from trying
>to make detailed corrections, as this would become tedious quickly.
>While much of this work could be done by the RFC editor, some of the
>editorial decisions will enter e.g. IANA registries, so the technical
>terms need to be decided now.  More importantly, understanding this
>document during its development process (including mine as a reviewer)
>may be hampered by its editorial shortcomings.
>
>** Minor Issues:
>
>My first editorial problem is with the title.  This address format is
>not embedded in IPv4, as the title wants to make us believe.  Instead,
>it is talking about an multicast address format for IPv6 that embeds
>an IPv4 multicast address.  (While this misleading naming repeats the
>same mistake that has been made in RFC 6052, at least there it is not
>part of the title.)

Med: Could you please suggest a better title?=20

>
>3
>
>The role of 64IX is very unclear.  My conjecture is that this draft is
>defining the address format for the case M=3D1 only (i.e., address[16] =3D
>1).  No text defines what happens for M=3D0, so the assumption appears
>to be that RFC 4291 applies unchanged in this case.  If this
>conjecture is correct, this needs to be made much clearer.

Med: The current text says: "When "M-bit" is set to 1, it indicates that a =
multicast
      IPv4 address is embedded in the low-order 32 bits of the multicast
      IPv6 address.". I can add: "When "M-bit" is set to 0, the address for=
mat follows [RFC4291].". Would this be fine with you?=20

>
>What is "r"?  Define.

Med: This means "reserved". The text says: "All the remaining bits are rese=
rved and MUST be set
      to 0.". Do you think the text should be clarified further?=20

>
>4
>
>Why is 64IX moving around here?
>(The discriminating bit M now seems to be address[32].)
>How does one find out which of the two positions of the M bit to use?

Med: Once the prefix is configured to a receiver, an IPv4-IPv6 PIM interwor=
king function, the question of the location of the M-bit is not relevant an=
ymore. If both ASM and SSM modes are supported, two prefixes will be used.=
=20

>
>.          o  sub-group-id: The default value is all zeros.
>How does an application find out when to choose a different one?

Med: Applications are provisioned with the full prefix; see Section 6.

>
>.             232.0.0.1-232.0.0.255 range is being
>.             reserved to IANA.
>Who is making this reservation?  ("is being reserved" means the
>resernation is going on right now, but I don't find anything in 9.)

Med: We removed that sentence as a result of a comment I received from SM (=
see mboned archives).

>
>7
>
>7 seems to imply this format is only useful where RFC 6052 is in use.
>If this is true, this should be clearly stated.  More specifically,
>the assumption appears to be that all nodes that need to exchange
>information that concerns IPv4 sources need to have the same RFC 6052
>parameters in effect.  How is that ensured?

Med: This is a generic issue for RFC6052. We can document the issue if it i=
s specific to the multicast context.=20

>
>** Nits:
>
>10 -- s/defined/defines/

Med: Fixed. Thanks.

>
>(And many more, see above.)
>
>=

From cabo@tzi.org  Wed May  9 11:20:44 2012
Return-Path: <cabo@tzi.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 7CACC11E80B4; Wed,  9 May 2012 11:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.287
X-Spam-Level: 
X-Spam-Status: No, score=-106.287 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 16U3zLxAEXGt; Wed,  9 May 2012 11:20:43 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 31F3811E80AB; Wed,  9 May 2012 11:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q49IKWVh020033; Wed, 9 May 2012 20:20:32 +0200 (CEST)
Received: from [192.168.217.105] (p548992D9.dip.t-dialin.net [84.137.146.217]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id E2EB35C1; Wed,  9 May 2012 20:20:31 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E29946F71@PUEXCB1B.nanterre.francetelecom.fr>
Date: Wed, 9 May 2012 20:20:35 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org>
References: <92309DC0-A179-4B5B-9D8C-4B55F64A4668@tzi.org> <94C682931C08B048B7A8645303FDC9F36E29946F71@PUEXCB1B.nanterre.francetelecom.fr>
To: <mohamed.boucadair@orange.com>
X-Mailer: Apple Mail (2.1257)
X-Mailman-Approved-At: Wed, 09 May 2012 11:53:46 -0700
Cc: "mboned@ietf.org" <mboned@ietf.org>, "6man@ietf.org" <6man@ietf.org>, The IESG <iesg@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 09 May 2012 18:20:44 -0000

Hi Med,

thanks for looking into my review.  Let me take this opportunity to =
reiterate that, while I wrote this review for the Applications Area =
Directorate, it is not intended to bear more weight than any other =
comment submitted by an individual during a Last Call.

> Med: There are plenty of applications using this address format: e.g., =
[I-D.ietf-softwire-mesh-multicast], =
[I-D.ietf-softwire-dslite-multicast], =
[I-D.ietf-softwire-multicast-prefix-option], =
[I-D.venaas-behave-v4v6mc-framework],  =
[I-D.sarikaya-behave-netext-nat64-pmip], =
[I-D.sarikaya-behave-mext-nat64-dsmip], etc. We had pointers to some of =
those drafts in earlier versions of the document but we removed them and =
adopted the same approach as RFC6052: only the address format is defined =
while the usage is defined in companion documents.

The problem with this is that you now have a bit allocation without any =
semantics.
What is different, then, from any other way to allocate multicast =
addresses?
If you want this part of the address space to have some specific =
semantics, you have to give it some.

> More details are also documented here: =
http://tools.ietf.org/html/draft-boucadair-behave-64-multicast-address-for=
mat-03#appendix-A.1 and =
http://tools.ietf.org/html/draft-boucadair-behave-64-multicast-address-for=
mat-03#appendix-A.2.=20
>=20
> There is also a problem statement, available at: =
http://tools.ietf.org/html/draft-jaclee-behave-v4v6-mcast-ps-03 which =
can be cited in the introduction.=20

I do believe that there needs to be some indication in the document.
Maybe some of the material from the problem statement can be put into an =
appendix.
BTW, what is the plan with the problem statement document?  Was this too =
contentious to make it a WG document?

>> ** Major Issues:
>>=20
>> To continue the summary: I don't understand which network elements
>> need to be able to determine, by looking at an IP address, that this
>> document is in use.  What for?  More generally, which entities need =
to
>> interoperate based on a common understanding of this format?
>=20
> Med: Elements which make use of the address format are =
deployment-specific; this can be a receiver, an IPv4-IPv6 PIM =
interworking function, IGMP/MLD Interworking function. We didn't quoted =
these interworking functions because this is deployment-specific. Do you =
think your issue can be solved if we add a pointer to one of the =
solutions documented listed above?

So the idea is that this is a common format that can be used by any =
number of transition mechanisms?
How do you avoid the mechanisms getting confused (e.g., one mechanism =
allocating an address that is then processed incorrectly by a network =
element that is using another mechanism)?

Yes, I think standardizing this document in a cluster with one or more =
transition mechanism documents and adding mutual references would be the =
best way to handle this.  As long as the question above has a good =
answer...

>> Of the various fields left "configurable according to local policies
>> of the entity managing the IPv4-IPv6 Interconnection Function", which
>> are important for applications?  How do they know these policies?
>=20
> Med: The content of this filed is left configurable. Its value will =
depend on the policies enforced by the administrative entity. Examples =
of these policies are: embedded-RF, use unicast-based prefix, etc. =
Applications are not aware of these policies since a prefix will (likely =
/96) will be provisioned (see Section 6).
>=20
>  If
>> that information is all in the two parameters "ASM_MPREFIX64" and
>> "SSM_MPREFIX64", what is the protocol that will be used to make this
>> information available to applications?  I don't think this can be a
>> standards-track document without defining at least one MTI protocol
>> for disseminating this information.
>=20
> Med: The provisioning of the ASM_PREFIX64 and the SSM_PREFIX is =
orthogonal to the address format itself. Various methods can be used but =
this is out of scope of the document. We can add a pointer to =
http://tools.ietf.org/html/draft-ietf-softwire-multicast-prefix-option-00 =
as a provisioning example. Would you be fine with adding such reference?

Are there any requirements on the provisioning mechanism to maintain the =
integrity of the semantics you desire?
I think the format just needs to state those.
Pointing to a protocol as an existence proof would also be an =
improvement.

>  What is an implementation
>> supposed to do that receives an address that looks like it is =
governed
>> by this document but does not conform to either of the agreed
>> prefixes disseminated to the implementation?
>=20
> Med: This is an issue for the provisioning method and not for the =
specification of the address format itself.

I'm not sure about that.  If I get a conflicting address using some =
control protocol, should I deny that?  Just go ahead anyway?
Will this confuse the network elements performing the transition =
mechanisms?
(My questions may sound very theoretic, but that is because the draft =
just doesn't tell me enough to even know whether these are good =
questions.)

> Med: Could you please suggest a better title?=20

Well, given that RFC 6052 already uses "IPv4-embedded" in what I read as =
the inverted semantics, this naming is hard to fix.
But maybe

	IPv6 Multicast Address Format With Embedded IPv4 Multicast =
Address=20

is not too long and much less ambiguous.

>> 3
>>=20
>> The role of 64IX is very unclear.  My conjecture is that this draft =
is
>> defining the address format for the case M=3D1 only (i.e., =
address[16] =3D
>> 1).  No text defines what happens for M=3D0, so the assumption =
appears
>> to be that RFC 4291 applies unchanged in this case.  If this
>> conjecture is correct, this needs to be made much clearer.
>=20
> Med: The current text says: "When "M-bit" is set to 1, it indicates =
that a multicast
>      IPv4 address is embedded in the low-order 32 bits of the =
multicast
>      IPv6 address.". I can add: "When "M-bit" is set to 0, the address =
format follows [RFC4291].". Would this be fine with you?=20

Yes, maybe make even more explicit that this document just governs those =
addresses where the M bit is set to 1.

>> What is "r"?  Define.
>=20
> Med: This means "reserved". The text says: "All the remaining bits are =
reserved and MUST be set
>      to 0.". Do you think the text should be clarified further?=20

Yes.  I think you should not talk about a "64IX" nibble at all (which =
then requires you to reserve three of those four bits) but just talk =
about the one M bit that you are assigning semantics to.

>> 4
>>=20
>> Why is 64IX moving around here?
>> (The discriminating bit M now seems to be address[32].)
>> How does one find out which of the two positions of the M bit to use?
>=20
> Med: Once the prefix is configured to a receiver, an IPv4-IPv6 PIM =
interworking function, the question of the location of the M-bit is not =
relevant anymore. If both ASM and SSM modes are supported, two prefixes =
will be used.=20

Again, that is true if all network elements agree on the provisioned =
prefixes.
But if they do, what is the point of this document?
Just saying "transition mechanisms can allocate a 96-bit prefix to which =
a 32-bit IPv4 multicast address is appended" would be enough then, no?

I get the idea that people want to write code that looks at this bit and =
exhibits different behavior based on whether it is set or not.
If that is not the case, there is no need for that bit...

>> .          o  sub-group-id: The default value is all zeros.
>> How does an application find out when to choose a different one?
>=20
> Med: Applications are provisioned with the full prefix; see Section 6.

But what does "default value" mean then?  Who is doing the defaulting, =
and what does it mean to use the default or to not use it?

>> .             232.0.0.1-232.0.0.255 range is being
>> .             reserved to IANA.
>> Who is making this reservation?  ("is being reserved" means the
>> resernation is going on right now, but I don't find anything in 9.)
>=20
> Med: We removed that sentence as a result of a comment I received from =
SM (see mboned archives).

Fine.

>> 7
>>=20
>> 7 seems to imply this format is only useful where RFC 6052 is in use.
>> If this is true, this should be clearly stated.  More specifically,
>> the assumption appears to be that all nodes that need to exchange
>> information that concerns IPv4 sources need to have the same RFC 6052
>> parameters in effect.  How is that ensured?
>=20
> Med: This is a generic issue for RFC6052. We can document the issue if =
it is specific to the multicast context.=20

I actually think it is more interesting in the multicast case, because =
multicast can span multiple domains (where a unicast address is assigned =
to one node that is "in" a specific domain).

Gr=FC=DFe, Carsten


From Tina.Tsou.Zouting@huawei.com  Wed May  9 15:47:27 2012
Return-Path: <Tina.Tsou.Zouting@huawei.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 7E91A11E80C1; Wed,  9 May 2012 15:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.476
X-Spam-Level: 
X-Spam-Status: No, score=-2.476 tagged_above=-999 required=5 tests=[AWL=0.123,  BAYES_00=-2.599]
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 ow1gAZNqK8P0; Wed,  9 May 2012 15:47:26 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 42EEA11E8086; Wed,  9 May 2012 15:47:26 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFT08510; Wed, 09 May 2012 18:47:26 -0400 (EDT)
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 9 May 2012 15:44:38 -0700
Received: from SZXEML436-HUB.china.huawei.com (10.72.61.64) by dfweml404-hub.china.huawei.com (10.193.5.203) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 9 May 2012 15:44:36 -0700
Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.48]) by szxeml436-hub.china.huawei.com ([10.72.61.64]) with mapi id 14.01.0323.003; Thu, 10 May 2012 06:44:31 +0800
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Carsten Bormann <cabo@tzi.org>
Thread-Topic: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
Thread-Index: AQHNLhUlNH7HgXPKw06b6CUPyEH5epbCDmwE
Date: Wed, 9 May 2012 22:44:30 +0000
Message-ID: <D003B142-55BA-4DD6-B293-849CB828E1E6@huawei.com>
References: <92309DC0-A179-4B5B-9D8C-4B55F64A4668@tzi.org> <94C682931C08B048B7A8645303FDC9F36E29946F71@PUEXCB1B.nanterre.francetelecom.fr>, <9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org>
In-Reply-To: <9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "6man@ietf.org" <6man@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>, The IESG <iesg@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] APPSDIR review of	draft-ietf-mboned-64-multicast-address-format-01
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, 09 May 2012 22:47:27 -0000

Sent from my iPad

On May 9, 2012, at 11:54 AM, "Carsten Bormann" <cabo@tzi.org> wrote:

> Hi Med,
>=20
> thanks for looking into my review.  Let me take this opportunity to reite=
rate that, while I wrote this review for the Applications Area Directorate,=
 it is not intended to bear more weight than any other comment submitted by=
 an individual during a Last Call.
>=20
>> Med: There are plenty of applications using this address format: e.g., [=
I-D.ietf-softwire-mesh-multicast], [I-D.ietf-softwire-dslite-multicast], [I=
-D.ietf-softwire-multicast-prefix-option], [I-D.venaas-behave-v4v6mc-framew=
ork],  [I-D.sarikaya-behave-netext-nat64-pmip], [I-D.sarikaya-behave-mext-n=
at64-dsmip], etc. We had pointers to some of those drafts in earlier versio=
ns of the document but we removed them and adopted the same approach as RFC=
6052: only the address format is defined while the usage is defined in comp=
anion documents.
>=20
> The problem with this is that you now have a bit allocation without any s=
emantics.
> What is different, then, from any other way to allocate multicast address=
es?
> If you want this part of the address space to have some specific semantic=
s, you have to give it some.
>=20
>> More details are also documented here: http://tools.ietf.org/html/draft-=
boucadair-behave-64-multicast-address-format-03#appendix-A.1 and http://too=
ls.ietf.org/html/draft-boucadair-behave-64-multicast-address-format-03#appe=
ndix-A.2.=20
>>=20
>> There is also a problem statement, available at: http://tools.ietf.org/h=
tml/draft-jaclee-behave-v4v6-mcast-ps-03 which can be cited in the introduc=
tion.=20
>=20
> I do believe that there needs to be some indication in the document.
> Maybe some of the material from the problem statement can be put into an =
appendix.
> BTW, what is the plan with the problem statement document?  Was this too =
contentious to make it a WG document?
It's has been adopted as MBONED WG item. The authors will submit the WG dra=
ft soon.
>=20
>>> ** Major Issues:
>>>=20
>>> To continue the summary: I don't understand which network elements
>>> need to be able to determine, by looking at an IP address, that this
>>> document is in use.  What for?  More generally, which entities need to
>>> interoperate based on a common understanding of this format?
>>=20
>> Med: Elements which make use of the address format are deployment-specif=
ic; this can be a receiver, an IPv4-IPv6 PIM interworking function, IGMP/ML=
D Interworking function. We didn't quoted these interworking functions beca=
use this is deployment-specific. Do you think your issue can be solved if w=
e add a pointer to one of the solutions documented listed above?
>=20
> So the idea is that this is a common format that can be used by any numbe=
r of transition mechanisms?
> How do you avoid the mechanisms getting confused (e.g., one mechanism all=
ocating an address that is then processed incorrectly by a network element =
that is using another mechanism)?
>=20
> Yes, I think standardizing this document in a cluster with one or more tr=
ansition mechanism documents and adding mutual references would be the best=
 way to handle this.  As long as the question above has a good answer...
http://datatracker.ietf.org/doc/draft-perreault-mboned-igmp-mld-translation=
/
http://datatracker.ietf.org/doc/draft-taylor-pim-v4v6-translation/
>=20
>>> Of the various fields left "configurable according to local policies
>>> of the entity managing the IPv4-IPv6 Interconnection Function", which
>>> are important for applications?  How do they know these policies?
>>=20
>> Med: The content of this filed is left configurable. Its value will depe=
nd on the policies enforced by the administrative entity. Examples of these=
 policies are: embedded-RF, use unicast-based prefix, etc. Applications are=
 not aware of these policies since a prefix will (likely /96) will be provi=
sioned (see Section 6).
>>=20
>> If
>>> that information is all in the two parameters "ASM_MPREFIX64" and
>>> "SSM_MPREFIX64", what is the protocol that will be used to make this
>>> information available to applications?  I don't think this can be a
>>> standards-track document without defining at least one MTI protocol
>>> for disseminating this information.
>>=20
>> Med: The provisioning of the ASM_PREFIX64 and the SSM_PREFIX is orthogon=
al to the address format itself. Various methods can be used but this is ou=
t of scope of the document. We can add a pointer to http://tools.ietf.org/h=
tml/draft-ietf-softwire-multicast-prefix-option-00 as a provisioning exampl=
e. Would you be fine with adding such reference?
>=20
> Are there any requirements on the provisioning mechanism to maintain the =
integrity of the semantics you desire?
> I think the format just needs to state those.
> Pointing to a protocol as an existence proof would also be an improvement=
.
Good suggestion.
>=20
>> What is an implementation
>>> supposed to do that receives an address that looks like it is governed
>>> by this document but does not conform to either of the agreed
>>> prefixes disseminated to the implementation?
>>=20
>> Med: This is an issue for the provisioning method and not for the specif=
ication of the address format itself.
>=20
> I'm not sure about that.  If I get a conflicting address using some contr=
ol protocol, should I deny that?  Just go ahead anyway?
> Will this confuse the network elements performing the transition mechanis=
ms?
> (My questions may sound very theoretic, but that is because the draft jus=
t doesn't tell me enough to even know whether these are good questions.)
>=20
>> Med: Could you please suggest a better title?=20
>=20
> Well, given that RFC 6052 already uses "IPv4-embedded" in what I read as =
the inverted semantics, this naming is hard to fix.
> But maybe
>=20
>    IPv6 Multicast Address Format With Embedded IPv4 Multicast Address=20
>=20
> is not too long and much less ambiguous.
>=20
>>> 3
>>>=20
>>> The role of 64IX is very unclear.  My conjecture is that this draft is
>>> defining the address format for the case M=3D1 only (i.e., address[16] =
=3D
>>> 1).  No text defines what happens for M=3D0, so the assumption appears
>>> to be that RFC 4291 applies unchanged in this case.  If this
>>> conjecture is correct, this needs to be made much clearer.
>>=20
>> Med: The current text says: "When "M-bit" is set to 1, it indicates that=
 a multicast
>>     IPv4 address is embedded in the low-order 32 bits of the multicast
>>     IPv6 address.". I can add: "When "M-bit" is set to 0, the address fo=
rmat follows [RFC4291].". Would this be fine with you?=20
>=20
> Yes, maybe make even more explicit that this document just governs those =
addresses where the M bit is set to 1.
>=20
>>> What is "r"?  Define.
>>=20
>> Med: This means "reserved". The text says: "All the remaining bits are r=
eserved and MUST be set
>>     to 0.". Do you think the text should be clarified further?=20
>=20
> Yes.  I think you should not talk about a "64IX" nibble at all (which the=
n requires you to reserve three of those four bits) but just talk about the=
 one M bit that you are assigning semantics to.
>=20
>>> 4
>>>=20
>>> Why is 64IX moving around here?
>>> (The discriminating bit M now seems to be address[32].)
>>> How does one find out which of the two positions of the M bit to use?
>>=20
>> Med: Once the prefix is configured to a receiver, an IPv4-IPv6 PIM inter=
working function, the question of the location of the M-bit is not relevant=
 anymore. If both ASM and SSM modes are supported, two prefixes will be use=
d.=20
>=20
> Again, that is true if all network elements agree on the provisioned pref=
ixes.
> But if they do, what is the point of this document?
> Just saying "transition mechanisms can allocate a 96-bit prefix to which =
a 32-bit IPv4 multicast address is appended" would be enough then, no?
>=20
> I get the idea that people want to write code that looks at this bit and =
exhibits different behavior based on whether it is set or not.
> If that is not the case, there is no need for that bit...
>=20
>>> .          o  sub-group-id: The default value is all zeros.
>>> How does an application find out when to choose a different one?
>>=20
>> Med: Applications are provisioned with the full prefix; see Section 6.
>=20
> But what does "default value" mean then?  Who is doing the defaulting, an=
d what does it mean to use the default or to not use it?
>=20
>>> .             232.0.0.1-232.0.0.255 range is being
>>> .             reserved to IANA.
>>> Who is making this reservation?  ("is being reserved" means the
>>> resernation is going on right now, but I don't find anything in 9.)
>>=20
>> Med: We removed that sentence as a result of a comment I received from S=
M (see mboned archives).
>=20
> Fine.
>=20
>>> 7
>>>=20
>>> 7 seems to imply this format is only useful where RFC 6052 is in use.
>>> If this is true, this should be clearly stated.  More specifically,
>>> the assumption appears to be that all nodes that need to exchange
>>> information that concerns IPv4 sources need to have the same RFC 6052
>>> parameters in effect.  How is that ensured?
>>=20
>> Med: This is a generic issue for RFC6052. We can document the issue if i=
t is specific to the multicast context.=20
>=20
> I actually think it is more interesting in the multicast case, because mu=
lticast can span multiple domains (where a unicast address is assigned to o=
ne node that is "in" a specific domain).
>=20
> Gr=FC=DFe, Carsten
>=20
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From yiu_lee@cable.comcast.com  Wed May  9 19:52:16 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 98B1E9E800B; Wed,  9 May 2012 19:52:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.722
X-Spam-Level: 
X-Spam-Status: No, score=-102.722 tagged_above=-999 required=5 tests=[AWL=2.509, 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 sSGapeih4jJP; Wed,  9 May 2012 19:52:15 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 7F92C9E8006; Wed,  9 May 2012 19:52:15 -0700 (PDT)
Received: from ([24.40.56.115]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.16727490; Wed, 09 May 2012 20:37:35 -0600
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0283.003; Wed, 9 May 2012 22:52:11 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Carsten Bormann <cabo@tzi.org>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Thread-Topic: APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
Thread-Index: AQHNLlfkes/D+SuV6UexlvBrmJ/rJg==
Date: Thu, 10 May 2012 02:52:10 +0000
Message-ID: <CBD0A398.20BF2%yiu_lee@cable.comcast.com>
In-Reply-To: <9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.1.120420
x-originating-ip: [24.40.55.71]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3419448728_1036269"
MIME-Version: 1.0
Cc: "mboned@ietf.org" <mboned@ietf.org>, "6man@ietf.org" <6man@ietf.org>, The IESG <iesg@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 10 May 2012 02:52:16 -0000

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

Hi Carsten,

Thanks very much for reviewing the document. I just want to add a point to
your question about how applications decide when to use this multicast
address format. In fact, they don't. Imagine a use case where a legacy
IPv4 IP-TV receiver (an app) wants to join a channel which is broadcasted
in IPv6. The app will continue to send the igmp-join (say 224.1.2.3).
There will be a function in the network which is statically configured
that when it receives a igmp-join, it would covert to a corresponding
mld-join. The IPv6 address in the join message will follow what is
described in this draft. This Adaptive Function is transparent to the
application and managed by the network.

Thanks,
Yiu

On 5/9/12 2:20 PM, "Carsten Bormann" <cabo@tzi.org> wrote:

>The problem with this is that you now have a bit allocation without any
>semantics.
>What is different, then, from any other way to allocate multicast
>addresses?
>If you want this part of the address space to have some specific
>semantics, you have to give it some.

--B_3419448728_1036269
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
Q0ECEFObm9wZOtwg92e9VN7esOQwCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJBDEWBBSkZiUh
umhrUS/ZRDnPDjRcWI4XIjAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ
BTEPFw0xMjA1MTAwMjUyMDZaMA0GCSqGSIb3DQEBAQUABIIBAE7b/YXBrdiPBGrbhLOdC6M7
9fnUcul9rPI9u7VRkZqxcMFLXfV8qh7HBZBVsObMwzkZUecVWRlQiP5IJyVlA/AowkpjvSqP
uW7oCBOKRD6NyE9Tz7Vf6xyED7fY3WrUs97ykp4bkBURqeheAyPlkeZPUXZ/DtATvUolmGqI
tdlel7AWO/CqvKZDX2VlclgjNJatyKKZfd9fJURolC+k4rV1v5EaIy6JQ6V8sg8kW9siD49J
uQ8s486ltEpCVHI67fvtG52VxvvC8mCIlH+2naZYNxVL8ABA/5omwepQYwcs9ZhVzPJUCazY
mhsotOTgCXPy6HMv7vKdlus/BzKTLb4=

--B_3419448728_1036269--

From jacni@jacni.com  Wed May  9 23:21:04 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 D58A321F85B8; Wed,  9 May 2012 23:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.806
X-Spam-Level: 
X-Spam-Status: No, score=-1.806 tagged_above=-999 required=5 tests=[AWL=0.481,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=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 pH7rL6r5hIpR; Wed,  9 May 2012 23:21:00 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id CFEA721F85B4; Wed,  9 May 2012 23:20:59 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 3E91D3800C9; Thu, 10 May 2012 02:20:57 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with ESMTP id C24F7340077; Thu, 10 May 2012 14:20:55 +0800 (CST)
Received: from [10.140.20.59] (unknown [64.104.125.217]) by app (Coremail) with SMTP id +AWowJAL6wVEXqtPWbrrAA--.19050S2; Thu, 10 May 2012 14:20:53 +0800 (CST)
Message-ID: <4FAB5E40.7080809@jacni.com>
Date: Thu, 10 May 2012 14:20:48 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
References: <92309DC0-A179-4B5B-9D8C-4B55F64A4668@tzi.org> <94C682931C08B048B7A8645303FDC9F36E29946F71@PUEXCB1B.nanterre.francetelecom.fr> <9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org>
In-Reply-To: <9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org>
Content-Type: multipart/alternative; boundary="------------080101020101010503000406"
X-CM-TRANSID: +AWowJAL6wVEXqtPWbrrAA--.19050S2
X-Coremail-Antispam: 1UD129KBjvJXoW3JFy5Aw1Dury8WrW8Wr4UJwb_yoW3GrW5pa y3Krs8KF1kJw1rCw4kZw18Wr1F9Fs5trW7KFW5K34UZws8Kr1IvF4Fkw4Y9a4DWr95Za1j vr4akrn8Za4qyaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnL8YjsxI4VWkKwAYFVCjjxCrM7CY07I20VC2zVCF04k26cxKx2IYs7xG 6rWj6s0DMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8JwACjcxG0x vEwIxGrwCjr7xvwVCIw2I0I7xG6c02F41lc7I2V7IY0VAS07AlzVAYIcxG8wCF04k20xvY 0x0EwIxGrwC2zVAF1VAY17CE14v26r126r1DMIIYrxkI7VAKI48JYxBIdaVFxhVjvjDU0x ZFpf9x07jwPEfUUUUU=
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQAKEko7lQ825AABsh
Cc: "6man@ietf.org" <6man@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>, The IESG <iesg@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 10 May 2012 06:21:04 -0000

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

Hi Carsten,

Thanks a lot for your comments, please see inline below.

On 5/10/2012 Thursday 2:20 AM, Carsten Bormann wrote:
> Hi Med,
>
> thanks for looking into my review.  Let me take this opportunity to reiterate that, while I wrote this review for the Applications Area Directorate, it is not intended to bear more weight than any other comment submitted by an individual during a Last Call.
>
>> Med: There are plenty of applications using this address format: e.g., [I-D.ietf-softwire-mesh-multicast], [I-D.ietf-softwire-dslite-multicast], [I-D.ietf-softwire-multicast-prefix-option], [I-D.venaas-behave-v4v6mc-framework],  [I-D.sarikaya-behave-netext-nat64-pmip], [I-D.sarikaya-behave-mext-nat64-dsmip], etc. We had pointers to some of those drafts in earlier versions of the document but we removed them and adopted the same approach as RFC6052: only the address format is defined while the usage is defined in companion documents.
> The problem with this is that you now have a bit allocation without any semantics.
> What is different, then, from any other way to allocate multicast addresses?
> If you want this part of the address space to have some specific semantics, you have to give it some.
For the semantics, you can see YIu's point. More specifically, for 
example, some adaptive/interworking function of network elements can 
interpret it as, if the M bit is set 1, then pick the corresponding IPv4 
group address.

>>> ** Major Issues:
>>>
>>> To continue the summary: I don't understand which network elements
>>> need to be able to determine, by looking at an IP address, that this
>>> document is in use.  What for?  More generally, which entities need to
>>> interoperate based on a common understanding of this format?
>> Med: Elements which make use of the address format are deployment-specific; this can be a receiver, an IPv4-IPv6 PIM interworking function, IGMP/MLD Interworking function. We didn't quoted these interworking functions because this is deployment-specific. Do you think your issue can be solved if we add a pointer to one of the solutions documented listed above?
> So the idea is that this is a common format that can be used by any number of transition mechanisms?
> How do you avoid the mechanisms getting confused (e.g., one mechanism allocating an address that is then processed incorrectly by a network element that is using another mechanism)?
Not sure whether I understand your question here correctly, but let me 
try to,
The address/prefix allocating should be an independent component of the 
service provisioning, and should just make a consistent assignment of 
the block throughout the related elements. The format standardized is 
for the elements to perform the adaptive function without any coordination.

> Yes, I think standardizing this document in a cluster with one or more transition mechanism documents and adding mutual references would be the best way to handle this.  As long as the question above has a good answer...
>
>
>   If
>>> that information is all in the two parameters "ASM_MPREFIX64" and
>>> "SSM_MPREFIX64", what is the protocol that will be used to make this
>>> information available to applications?  I don't think this can be a
>>> standards-track document without defining at least one MTI protocol
>>> for disseminating this information.
>> Med: The provisioning of the ASM_PREFIX64 and the SSM_PREFIX is orthogonal to the address format itself. Various methods can be used but this is out of scope of the document. We can add a pointer to http://tools.ietf.org/html/draft-ietf-softwire-multicast-prefix-option-00 as a provisioning example. Would you be fine with adding such reference?
> Are there any requirements on the provisioning mechanism to maintain the integrity of the semantics you desire?
> I think the format just needs to state those.
I guess standardizing the format is to maintain the integrity of the 
semantics. For the responsibility of address/prefix provisioning 
mechanism, please see my response above.
Or maybe I misunderstand your question?

> Pointing to a protocol as an existence proof would also be an improvement.
>
>>   What is an implementation
>>> supposed to do that receives an address that looks like it is governed
>>> by this document but does not conform to either of the agreed
>>> prefixes disseminated to the implementation?
>> Med: This is an issue for the provisioning method and not for the specification of the address format itself.
> I'm not sure about that.  If I get a conflicting address using some control protocol, should I deny that?  Just go ahead anyway?
> Will this confuse the network elements performing the transition mechanisms?
It should be in the scope of operations or deployment, to avoid that.

> (My questions may sound very theoretic, but that is because the draft just doesn't tell me enough to even know whether these are good questions.)
>
>> Med: Could you please suggest a better title?
> Well, given that RFC 6052 already uses "IPv4-embedded" in what I read as the inverted semantics, this naming is hard to fix.
> But maybe
>
> 	IPv6 Multicast Address Format With Embedded IPv4 Multicast Address
>
> is not too long and much less ambiguous.
We'll consider it, thanks a lot.

>>> 4
>>>
>>> Why is 64IX moving around here?
>>> (The discriminating bit M now seems to be address[32].)
>>> How does one find out which of the two positions of the M bit to use?
>> Med: Once the prefix is configured to a receiver, an IPv4-IPv6 PIM interworking function, the question of the location of the M-bit is not relevant anymore. If both ASM and SSM modes are supported, two prefixes will be used.
> Again, that is true if all network elements agree on the provisioned prefixes.
> But if they do, what is the point of this document?
> Just saying "transition mechanisms can allocate a 96-bit prefix to which a 32-bit IPv4 multicast address is appended" would be enough then, no?
In this way, the elements have to maintain "states", and coordination is 
required. Even though, they also have to be told how to derive the IPv4 
multicast address embedded.

>
> I get the idea that people want to write code that looks at this bit and exhibits different behavior based on whether it is set or not.
> If that is not the case, there is no need for that bit...
>
>>> .          o  sub-group-id: The default value is all zeros.
>>> How does an application find out when to choose a different one?
>> Med: Applications are provisioned with the full prefix; see Section 6.
> But what does "default value" mean then?  Who is doing the defaulting, and what does it mean to use the default or to not use it?
It can mean, for example "if RFC3956, embedding RP in an IPv6 multicast 
address is not used".


Cheers,
Jacni

>>> 7
>>>
>>> 7 seems to imply this format is only useful where RFC 6052 is in use.
>>> If this is true, this should be clearly stated.  More specifically,
>>> the assumption appears to be that all nodes that need to exchange
>>> information that concerns IPv4 sources need to have the same RFC 6052
>>> parameters in effect.  How is that ensured?
>> Med: This is a generic issue for RFC6052. We can document the issue if it is specific to the multicast context.
> I actually think it is more interesting in the multicast case, because multicast can span multiple domains (where a unicast address is assigned to one node that is "in" a specific domain).
>
> Grüße, Carsten
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>
>

--------------080101020101010503000406
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">
    <font face="Calibri">Hi Carsten,<br>
      <br>
      Thanks a lot for your comments, please see inline below.<br>
    </font><br>
    On 5/10/2012 Thursday 2:20 AM, Carsten Bormann wrote:
    <blockquote cite="mid:9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org"
      type="cite">
      <pre wrap="">Hi Med,

thanks for looking into my review.  Let me take this opportunity to reiterate that, while I wrote this review for the Applications Area Directorate, it is not intended to bear more weight than any other comment submitted by an individual during a Last Call.

</pre>
      <blockquote type="cite">
        <pre wrap="">Med: There are plenty of applications using this address format: e.g., [I-D.ietf-softwire-mesh-multicast], [I-D.ietf-softwire-dslite-multicast], [I-D.ietf-softwire-multicast-prefix-option], [I-D.venaas-behave-v4v6mc-framework],  [I-D.sarikaya-behave-netext-nat64-pmip], [I-D.sarikaya-behave-mext-nat64-dsmip], etc. We had pointers to some of those drafts in earlier versions of the document but we removed them and adopted the same approach as RFC6052: only the address format is defined while the usage is defined in companion documents.
</pre>
      </blockquote>
      <pre wrap="">
The problem with this is that you now have a bit allocation without any semantics.
What is different, then, from any other way to allocate multicast addresses?
If you want this part of the address space to have some specific semantics, you have to give it some.
</pre>
    </blockquote>
    For the semantics, you can see YIu's point. More specifically, for
    example, some adaptive/interworking function of network elements can
    interpret it as, if the M bit is set 1, then pick the corresponding
    IPv4 group address.<br>
    <br>
    <blockquote cite="mid:9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org"
      type="cite">
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">** Major Issues:

To continue the summary: I don't understand which network elements
need to be able to determine, by looking at an IP address, that this
document is in use.  What for?  More generally, which entities need to
interoperate based on a common understanding of this format?
</pre>
        </blockquote>
        <pre wrap="">
Med: Elements which make use of the address format are deployment-specific; this can be a receiver, an IPv4-IPv6 PIM interworking function, IGMP/MLD Interworking function. We didn't quoted these interworking functions because this is deployment-specific. Do you think your issue can be solved if we add a pointer to one of the solutions documented listed above?
</pre>
      </blockquote>
      <pre wrap="">
So the idea is that this is a common format that can be used by any number of transition mechanisms?
How do you avoid the mechanisms getting confused (e.g., one mechanism allocating an address that is then processed incorrectly by a network element that is using another mechanism)?
</pre>
    </blockquote>
    Not sure whether I understand your question here correctly, but let
    me try to,<br>
    The address/prefix allocating should be an independent component of
    the service provisioning, and should just make a consistent
    assignment of the block throughout the related elements. The format
    standardized is for the elements to perform the adaptive function
    without any coordination.<br>
    <br>
    <blockquote cite="mid:9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org"
      type="cite">
      <pre wrap="">
Yes, I think standardizing this document in a cluster with one or more transition mechanism documents and adding mutual references would be the best way to handle this.  As long as the question above has a good answer...


 If
</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">that information is all in the two parameters "ASM_MPREFIX64" and
"SSM_MPREFIX64", what is the protocol that will be used to make this
information available to applications?  I don't think this can be a
standards-track document without defining at least one MTI protocol
for disseminating this information.
</pre>
        </blockquote>
        <pre wrap="">
Med: The provisioning of the ASM_PREFIX64 and the SSM_PREFIX is orthogonal to the address format itself. Various methods can be used but this is out of scope of the document. We can add a pointer to <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-softwire-multicast-prefix-option-00">http://tools.ietf.org/html/draft-ietf-softwire-multicast-prefix-option-00</a> as a provisioning example. Would you be fine with adding such reference?
</pre>
      </blockquote>
      <pre wrap="">
Are there any requirements on the provisioning mechanism to maintain the integrity of the semantics you desire?
I think the format just needs to state those.</pre>
    </blockquote>
    I guess standardizing the format is to maintain the integrity of the
    semantics. For the responsibility of address/prefix provisioning
    mechanism, please see my response above.<br>
    Or maybe I misunderstand your question?<br>
    <br>
    <blockquote cite="mid:9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org"
      type="cite">
      <pre wrap="">
Pointing to a protocol as an existence proof would also be an improvement.

</pre>
      <blockquote type="cite">
        <pre wrap=""> What is an implementation
</pre>
        <blockquote type="cite">
          <pre wrap="">supposed to do that receives an address that looks like it is governed
by this document but does not conform to either of the agreed
prefixes disseminated to the implementation?
</pre>
        </blockquote>
        <pre wrap="">
Med: This is an issue for the provisioning method and not for the specification of the address format itself.
</pre>
      </blockquote>
      <pre wrap="">
I'm not sure about that.  If I get a conflicting address using some control protocol, should I deny that?  Just go ahead anyway?
Will this confuse the network elements performing the transition mechanisms?</pre>
    </blockquote>
    It should be in the scope of operations or deployment, to avoid
    that.<br>
    <br>
    <blockquote cite="mid:9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org"
      type="cite">
      <pre wrap="">
(My questions may sound very theoretic, but that is because the draft just doesn't tell me enough to even know whether these are good questions.)

</pre>
      <blockquote type="cite">
        <pre wrap="">Med: Could you please suggest a better title? 
</pre>
      </blockquote>
      <pre wrap="">
Well, given that RFC 6052 already uses "IPv4-embedded" in what I read as the inverted semantics, this naming is hard to fix.
But maybe

	IPv6 Multicast Address Format With Embedded IPv4 Multicast Address 

is not too long and much less ambiguous.
</pre>
    </blockquote>
    We'll consider it, thanks a lot.<br>
    <br>
    <blockquote cite="mid:9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org"
      type="cite">
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">4

Why is 64IX moving around here?
(The discriminating bit M now seems to be address[32].)
How does one find out which of the two positions of the M bit to use?
</pre>
        </blockquote>
        <pre wrap="">
Med: Once the prefix is configured to a receiver, an IPv4-IPv6 PIM interworking function, the question of the location of the M-bit is not relevant anymore. If both ASM and SSM modes are supported, two prefixes will be used. 
</pre>
      </blockquote>
      <pre wrap="">
Again, that is true if all network elements agree on the provisioned prefixes.
But if they do, what is the point of this document?
Just saying "transition mechanisms can allocate a 96-bit prefix to which a 32-bit IPv4 multicast address is appended" would be enough then, no?</pre>
    </blockquote>
    In this way, the elements have to maintain "states", and
    coordination is required. Even though, they also have to be told how
    to derive the IPv4 multicast address embedded.<br>
    <br>
    <blockquote cite="mid:9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org"
      type="cite">
      <pre wrap="">

I get the idea that people want to write code that looks at this bit and exhibits different behavior based on whether it is set or not.
If that is not the case, there is no need for that bit...

</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">.          o  sub-group-id: The default value is all zeros.
How does an application find out when to choose a different one?
</pre>
        </blockquote>
        <pre wrap="">
Med: Applications are provisioned with the full prefix; see Section 6.
</pre>
      </blockquote>
      <pre wrap="">
But what does "default value" mean then?  Who is doing the defaulting, and what does it mean to use the default or to not use it?
</pre>
    </blockquote>
    It can mean, for example "if RFC3956, embedding RP in an IPv6
    multicast address is not used".<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote cite="mid:9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org"
      type="cite">
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">7

7 seems to imply this format is only useful where RFC 6052 is in use.
If this is true, this should be clearly stated.  More specifically,
the assumption appears to be that all nodes that need to exchange
information that concerns IPv4 sources need to have the same RFC 6052
parameters in effect.  How is that ensured?
</pre>
        </blockquote>
        <pre wrap="">
Med: This is a generic issue for RFC6052. We can document the issue if it is specific to the multicast context. 
</pre>
      </blockquote>
      <pre wrap="">
I actually think it is more interesting in the multicast case, because multicast can span multiple domains (where a unicast address is assigned to one node that is "in" a specific domain).

Gr&uuml;&szlig;e, Carsten

_______________________________________________
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>
  </body>
</html>

--------------080101020101010503000406--


From mohamed.boucadair@orange.com  Thu May 10 02:12:03 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 10EA021F85FC; Thu, 10 May 2012 02:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level: 
X-Spam-Status: No, score=-2.093 tagged_above=-999 required=5 tests=[AWL=0.155,  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 DqowR4Qr8rV6; Thu, 10 May 2012 02:12:01 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 3493621F85F8; Thu, 10 May 2012 02:12:01 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm10.si.francetelecom.fr (ESMTP service) with ESMTP id 977DF264498; Thu, 10 May 2012 11:12:00 +0200 (CEST)
Received: from PUEXCH11.nanterre.francetelecom.fr (unknown [10.101.44.27]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 777F127C057; Thu, 10 May 2012 11:12:00 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH11.nanterre.francetelecom.fr ([10.101.44.27]) with mapi; Thu, 10 May 2012 11:12:00 +0200
From: <mohamed.boucadair@orange.com>
To: Carsten Bormann <cabo@tzi.org>
Date: Thu, 10 May 2012 11:11:58 +0200
Thread-Topic: APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
Thread-Index: Ac0uEHTRtaVl85H2Tjm7beWGJ+xMzgAc2mIg
Message-ID: <94C682931C08B048B7A8645303FDC9F36E2A52C67B@PUEXCB1B.nanterre.francetelecom.fr>
References: <92309DC0-A179-4B5B-9D8C-4B55F64A4668@tzi.org> <94C682931C08B048B7A8645303FDC9F36E29946F71@PUEXCB1B.nanterre.francetelecom.fr> <9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org>
In-Reply-To: <9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org>
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.5.10.73320
Cc: "mboned@ietf.org" <mboned@ietf.org>, "6man@ietf.org" <6man@ietf.org>, The IESG <iesg@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 10 May 2012 09:12:03 -0000

Dear Carsten,

Please see inline.=20

Cheers,
Med=20

>-----Message d'origine-----
>De : Carsten Bormann [mailto:cabo@tzi.org]=20
>Envoy=E9 : mercredi 9 mai 2012 20:21
>=C0 : BOUCADAIR Mohamed OLNC/NAD/TIP
>Cc :=20
>draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.or
>g; apps-discuss@ietf.org application-layer protocols; The=20
>IESG; 6man@ietf.org; mboned@ietf.org
>Objet : Re: APPSDIR review of=20
>draft-ietf-mboned-64-multicast-address-format-01
>
>Hi Med,
>
>thanks for looking into my review.  Let me take this=20
>opportunity to reiterate that, while I wrote this review for=20
>the Applications Area Directorate, it is not intended to bear=20
>more weight than any other comment submitted by an individual=20
>during a Last Call.
>
>> Med: There are plenty of applications using this address=20
>format: e.g., [I-D.ietf-softwire-mesh-multicast],=20
>[I-D.ietf-softwire-dslite-multicast],=20
>[I-D.ietf-softwire-multicast-prefix-option],=20
>[I-D.venaas-behave-v4v6mc-framework], =20
>[I-D.sarikaya-behave-netext-nat64-pmip],=20
>[I-D.sarikaya-behave-mext-nat64-dsmip], etc. We had pointers=20
>to some of those drafts in earlier versions of the document=20
>but we removed them and adopted the same approach as RFC6052:=20
>only the address format is defined while the usage is defined=20
>in companion documents.
>
>The problem with this is that you now have a bit allocation=20
>without any semantics.
>What is different, then, from any other way to allocate=20
>multicast addresses?
>If you want this part of the address space to have some=20
>specific semantics, you have to give it some.

Med: Ok. I'm planning to do these changes:

(a) Re-insert this appendix: http://tools.ietf.org/html/draft-boucadair-beh=
ave-64-multicast-address-format-03#appendix-A.2 and a reference to it in th=
e introduction?

(b) Add this text to the introduction:

   Recently various solutions (e.g., [I-D.venaas-behave-v4v6mc-framework],
   [I-D.ietf-softwire-mesh-multicast] or [I-D.ietf-softwire-dslite-multicas=
t]) have been proposed to allow
   access to IPv4 multicast content from hosts attached to IPv6-enabled
   domains.

   Even if these solutions have distinct applicability scopes
   (translation vs. encapsulation) and target different use cases, they
   all make use of specific IPv6 multicast addresses to embed an IPv4
   multicast address.  Particularly, the IPv4-embedded IPv6 multicast
   address is used as a destination IPv6 address of multicast flows
   received from an IPv4-enabled domain and injected by the IPv4-IPv6
   Interconnection Function into an IPv6-enabled domain.  It is also
   used to build an IPv6 multicast state (*, G6) or (S6, G6)
   corresponding to their (*, G4) or (S4, G4) IPv4 counter parts by the
   IPv4-IPv6 Interconnection Function.

Are you OK with these proposed changes?

>
>> More details are also documented here:=20
>http://tools.ietf.org/html/draft-boucadair-behave-64-multicast-
>address-format-03#appendix-A.1 and=20
>http://tools.ietf.org/html/draft-boucadair-behave-64-multicast-
>address-format-03#appendix-A.2.=20
>>=20
>> There is also a problem statement, available at:=20
>http://tools.ietf.org/html/draft-jaclee-behave-v4v6-mcast-ps-03
> which can be cited in the introduction.=20
>
>I do believe that there needs to be some indication in the document.
>Maybe some of the material from the problem statement can be=20
>put into an appendix.
>BTW, what is the plan with the problem statement document? =20
>Was this too contentious to make it a WG document?

Med: The problem statement document has been adopted as an mboned WG docume=
nt. I added this sentence:

   More discussion about issues related to IPv4/IPv6 multicast can be
   found at [I-D.jaclee-behave-v4v6-mcast-ps].


>
>>> ** Major Issues:
>>>=20
>>> To continue the summary: I don't understand which network elements
>>> need to be able to determine, by looking at an IP address, that this
>>> document is in use.  What for?  More generally, which=20
>entities need to
>>> interoperate based on a common understanding of this format?
>>=20
>> Med: Elements which make use of the address format are=20
>deployment-specific; this can be a receiver, an IPv4-IPv6 PIM=20
>interworking function, IGMP/MLD Interworking function. We=20
>didn't quoted these interworking functions because this is=20
>deployment-specific. Do you think your issue can be solved if=20
>we add a pointer to one of the solutions documented listed above?
>
>So the idea is that this is a common format that can be used=20
>by any number of transition mechanisms?
>How do you avoid the mechanisms getting confused (e.g., one=20
>mechanism allocating an address that is then processed=20
>incorrectly by a network element that is using another mechanism)?

Med: What do you think is needed to be added to http://tools.ietf.org/html/=
draft-ietf-mboned-64-multicast-address-format-01#section-6? Thanks.

>
>Yes, I think standardizing this document in a cluster with one=20
>or more transition mechanism documents and adding mutual=20
>references would be the best way to handle this.  As long as=20
>the question above has a good answer...
>
>>> Of the various fields left "configurable according to local policies
>>> of the entity managing the IPv4-IPv6 Interconnection=20
>Function", which
>>> are important for applications?  How do they know these policies?
>>=20
>> Med: The content of this filed is left configurable. Its=20
>value will depend on the policies enforced by the=20
>administrative entity. Examples of these policies are:=20
>embedded-RF, use unicast-based prefix, etc. Applications are=20
>not aware of these policies since a prefix will (likely /96)=20
>will be provisioned (see Section 6).
>>=20
>>  If
>>> that information is all in the two parameters "ASM_MPREFIX64" and
>>> "SSM_MPREFIX64", what is the protocol that will be used to make this
>>> information available to applications?  I don't think this can be a
>>> standards-track document without defining at least one MTI protocol
>>> for disseminating this information.
>>=20
>> Med: The provisioning of the ASM_PREFIX64 and the SSM_PREFIX=20
>is orthogonal to the address format itself. Various methods=20
>can be used but this is out of scope of the document. We can=20
>add a pointer to=20
>http://tools.ietf.org/html/draft-ietf-softwire-multicast-prefix
>-option-00 as a provisioning example. Would you be fine with=20
>adding such reference?
>
>Are there any requirements on the provisioning mechanism to=20
>maintain the integrity of the semantics you desire?

Med: The provisioning mechanism (e.g., dhcp, netconf, etc.) is not "aware" =
of the semantic. There are no specific requirements compared to another pro=
visioning context. If your comment is related to http://tools.ietf.org/html=
/rfc6052#section-5.2, this is already captured in the Security Consideratio=
ns section.

>I think the format just needs to state those.
>Pointing to a protocol as an existence proof would also be an=20
>improvement.

Med: I added a I-D.ietf-softwire-multicast-prefix-option as an informative =
reference.

>
>>  What is an implementation
>>> supposed to do that receives an address that looks like it=20
>is governed
>>> by this document but does not conform to either of the agreed
>>> prefixes disseminated to the implementation?
>>=20
>> Med: This is an issue for the provisioning method and not=20
>for the specification of the address format itself.
>
>I'm not sure about that.  If I get a conflicting address using=20
>some control protocol, should I deny that?  Just go ahead anyway?
>Will this confuse the network elements performing the=20
>transition mechanisms?

Med: The current text says that up to 2 MPREFIX64 can be provisioned; one p=
refix for ASM and another one for SSM. Just like any other configurable par=
ameter, the value of these parameters will be set to the latest (valid) enf=
orced configuration. I still don't see what I can add to Section 6.=20
=20

>(My questions may sound very theoretic, but that is because=20
>the draft just doesn't tell me enough to even know whether=20
>these are good questions.)
>
>> Med: Could you please suggest a better title?=20
>
>Well, given that RFC 6052 already uses "IPv4-embedded" in what=20
>I read as the inverted semantics, this naming is hard to fix.
>But maybe
>
>	IPv6 Multicast Address Format With Embedded IPv4=20
>Multicast Address=20
>
>is not too long and much less ambiguous.

Med: Thanks. I updated the text.

>
>>> 3
>>>=20
>>> The role of 64IX is very unclear.  My conjecture is that=20
>this draft is
>>> defining the address format for the case M=3D1 only (i.e.,=20
>address[16] =3D
>>> 1).  No text defines what happens for M=3D0, so the assumption appears
>>> to be that RFC 4291 applies unchanged in this case.  If this
>>> conjecture is correct, this needs to be made much clearer.
>>=20
>> Med: The current text says: "When "M-bit" is set to 1, it=20
>indicates that a multicast
>>      IPv4 address is embedded in the low-order 32 bits of=20
>the multicast
>>      IPv6 address.". I can add: "When "M-bit" is set to 0,=20
>the address format follows [RFC4291].". Would this be fine with you?=20
>
>Yes, maybe make even more explicit that this document just=20
>governs those addresses where the M bit is set to 1.
>
>>> What is "r"?  Define.
>>=20
>> Med: This means "reserved". The text says: "All the=20
>remaining bits are reserved and MUST be set
>>      to 0.". Do you think the text should be clarified further?=20
>
>Yes.  I think you should not talk about a "64IX" nibble at all=20
>(which then requires you to reserve three of those four bits)=20
>but just talk about the one M bit that you are assigning semantics to.
>
>>> 4
>>>=20
>>> Why is 64IX moving around here?
>>> (The discriminating bit M now seems to be address[32].)
>>> How does one find out which of the two positions of the M=20
>bit to use?
>>=20
>> Med: Once the prefix is configured to a receiver, an=20
>IPv4-IPv6 PIM interworking function, the question of the=20
>location of the M-bit is not relevant anymore. If both ASM and=20
>SSM modes are supported, two prefixes will be used.=20
>
>Again, that is true if all network elements agree on the=20
>provisioned prefixes.
>But if they do, what is the point of this document?
>Just saying "transition mechanisms can allocate a 96-bit=20
>prefix to which a 32-bit IPv4 multicast address is appended"=20
>would be enough then, no?
>
>I get the idea that people want to write code that looks at=20
>this bit and exhibits different behavior based on whether it=20
>is set or not.
>If that is not the case, there is no need for that bit...
>
>>> .          o  sub-group-id: The default value is all zeros.
>>> How does an application find out when to choose a different one?
>>=20
>> Med: Applications are provisioned with the full prefix; see=20
>Section 6.
>
>But what does "default value" mean then?  Who is doing the=20
>defaulting, and what does it mean to use the default or to not use it?

Med: The entity managing the IPv4/IPv6 Interconnection function.

>
>>> .             232.0.0.1-232.0.0.255 range is being
>>> .             reserved to IANA.
>>> Who is making this reservation?  ("is being reserved" means the
>>> resernation is going on right now, but I don't find anything in 9.)
>>=20
>> Med: We removed that sentence as a result of a comment I=20
>received from SM (see mboned archives).
>
>Fine.
>
>>> 7
>>>=20
>>> 7 seems to imply this format is only useful where RFC 6052=20
>is in use.
>>> If this is true, this should be clearly stated.  More specifically,
>>> the assumption appears to be that all nodes that need to exchange
>>> information that concerns IPv4 sources need to have the=20
>same RFC 6052
>>> parameters in effect.  How is that ensured?
>>=20
>> Med: This is a generic issue for RFC6052. We can document=20
>the issue if it is specific to the multicast context.=20
>
>I actually think it is more interesting in the multicast case,=20
>because multicast can span multiple domains (where a unicast=20
>address is assigned to one node that is "in" a specific domain).
>

Med: Yes, but still this is a generic issue for RFC6052. Some deployment-sp=
ecific documents already covered this point: e.g., http://tools.ietf.org/ht=
ml/draft-ietf-softwire-dslite-multicast-02#section-5:=20

"The mAFTR and mB4 MUST use the
   same mPrefix64 and uPrefix64, as well as run the same algorithm for=20
   building IPv4-embedded IPv6 addresses."

Do you want to see a similar wording in the address format draft?=

From cabo@tzi.org  Thu May 10 04:01:11 2012
Return-Path: <cabo@tzi.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 E170721F867E; Thu, 10 May 2012 04:01:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.286
X-Spam-Level: 
X-Spam-Status: No, score=-106.286 tagged_above=-999 required=5 tests=[AWL=-0.037, BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 9qHumQq18toG; Thu, 10 May 2012 04:01:11 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 0BA6021F8678; Thu, 10 May 2012 04:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q4AB0h23009350; Thu, 10 May 2012 13:00:43 +0200 (CEST)
Received: from [192.168.217.117] (p5489AF8A.dip.t-dialin.net [84.137.175.138]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 0BD3C8F0; Thu, 10 May 2012 13:00:42 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <D003B142-55BA-4DD6-B293-849CB828E1E6@huawei.com>
Date: Thu, 10 May 2012 13:00:45 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C808362C-EA9A-4AC7-8CD0-19DC943DB02F@tzi.org>
References: <92309DC0-A179-4B5B-9D8C-4B55F64A4668@tzi.org> <94C682931C08B048B7A8645303FDC9F36E29946F71@PUEXCB1B.nanterre.francetelecom.fr> <9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org> <D003B142-55BA-4DD6-B293-849CB828E1E6@huawei.com>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
X-Mailer: Apple Mail (2.1257)
Cc: "6man@ietf.org" <6man@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>, The IESG <iesg@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 10 May 2012 11:01:12 -0000

Hi Tina,

thanks for the pointers.

On the problem statement, you say:

> It's has been adopted as MBONED WG item. The authors will submit the =
WG draft soon.

So I would normally expect the two documents (problem statement and =
normative spec) to go through as a cluster (if not the problem statement =
first).
Given the difference in advancement, that may be difficult to achieve, =
though; if that is not possible, the spec will need to provide some =
context by itself.

> =
http://datatracker.ietf.org/doc/draft-perreault-mboned-igmp-mld-translatio=
n/

This document reveals that the IPv4 multicast address embedded into the =
IPv6 multicast address is indeed used as such by applications on the =
other side of the mapper (5.2.4).
My main comment is that the mboned-64-multicast-address-format document =
does not even hint that this might be the case, much less defines =
semantics that might be used by an application on the IPv6 side (and =
there have been other comments that applications are not even involved =
on the IPv6 side, which doesn't quite seem to mesh with this document).

> http://datatracker.ietf.org/doc/draft-taylor-pim-v4v6-translation/

The latter is very clear in saying

   If an IPv6
   group address to be translated matches the format specified in that
   document for an IPv4-embedded IPv6 ASM or SSM group address, the
   corresponding IPv4 group address MUST be obtained by extracting the
   low-order 32 bits from the IPv6 address.  (The value of the sub-
   group-id field is irrelevant to this procedure.)=20

So that supports my conjecture that the following is a strong, unstated =
requirement on the format document:
It MUST be possible to determine, by looking at a packet, whether the =
destination IP address in there is matching the format or not.

This places an even stronger burden on the completeness of the =
specification than I initially thought.

I would address this by describing the algorithm that gets used to =
determine whether there is a match by looking at the packet.
(The fact that I cannot determine this algorithm even by educated =
guessing is my other main comment.)

Gr=FC=DFe, Carsten


From mohamed.boucadair@orange.com  Thu May 10 05:09:20 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 6AC1F21F852A; Thu, 10 May 2012 05:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[AWL=0.151,  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 dEe-Ri46AX10; Thu, 10 May 2012 05:09:19 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 8210C21F8527; Thu, 10 May 2012 05:09:19 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 46F5232463F; Thu, 10 May 2012 14:09:18 +0200 (CEST)
Received: from PUEXCH71.nanterre.francetelecom.fr (unknown [10.101.44.33]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 140F84C06F; Thu, 10 May 2012 14:09:18 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH71.nanterre.francetelecom.fr ([10.101.44.33]) with mapi; Thu, 10 May 2012 14:09:17 +0200
From: <mohamed.boucadair@orange.com>
To: Carsten Bormann <cabo@tzi.org>, Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Date: Thu, 10 May 2012 14:09:17 +0200
Thread-Topic: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
Thread-Index: Ac0unDb3juC9I39IRUSqsYZeuXzk7QAB/VwQ
Message-ID: <94C682931C08B048B7A8645303FDC9F36E2A52C755@PUEXCB1B.nanterre.francetelecom.fr>
References: <92309DC0-A179-4B5B-9D8C-4B55F64A4668@tzi.org> <94C682931C08B048B7A8645303FDC9F36E29946F71@PUEXCB1B.nanterre.francetelecom.fr> <9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org> <D003B142-55BA-4DD6-B293-849CB828E1E6@huawei.com> <C808362C-EA9A-4AC7-8CD0-19DC943DB02F@tzi.org>
In-Reply-To: <C808362C-EA9A-4AC7-8CD0-19DC943DB02F@tzi.org>
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.5.10.111522
Cc: "mboned@ietf.org" <mboned@ietf.org>, "6man@ietf.org" <6man@ietf.org>, The IESG <iesg@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 10 May 2012 12:09:20 -0000

Dear Cartsen,

The algorithm to extract the embedded IPv4 address is as follows:=20

If the multicast address belongs to ff3x:0:8000/33 or ffxx:8000/17, extract=
 the last 32 bits of the IPv6 address.

Are you suggesting to add such clarification to the address format I-D?

Cheers,
Med=20

>-----Message d'origine-----
>De : Carsten Bormann [mailto:cabo@tzi.org]=20
>Envoy=E9 : jeudi 10 mai 2012 13:01
>=C0 : Tina TSOU
>Cc : BOUCADAIR Mohamed OLNC/NAD/TIP; mboned@ietf.org;=20
>6man@ietf.org; The IESG; apps-discuss@ietf.org=20
>application-layer protocols;=20
>draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org
>Objet : Re: [MBONED] APPSDIR review of=20
>draft-ietf-mboned-64-multicast-address-format-01
>
>Hi Tina,
>
>thanks for the pointers.
>
>On the problem statement, you say:
>
>> It's has been adopted as MBONED WG item. The authors will=20
>submit the WG draft soon.
>
>So I would normally expect the two documents (problem=20
>statement and normative spec) to go through as a cluster (if=20
>not the problem statement first).
>Given the difference in advancement, that may be difficult to=20
>achieve, though; if that is not possible, the spec will need=20
>to provide some context by itself.
>
>>=20
>http://datatracker.ietf.org/doc/draft-perreault-mboned-igmp-mld
>-translation/
>
>This document reveals that the IPv4 multicast address embedded=20
>into the IPv6 multicast address is indeed used as such by=20
>applications on the other side of the mapper (5.2.4).
>My main comment is that the mboned-64-multicast-address-format=20
>document does not even hint that this might be the case, much=20
>less defines semantics that might be used by an application on=20
>the IPv6 side (and there have been other comments that=20
>applications are not even involved on the IPv6 side, which=20
>doesn't quite seem to mesh with this document).
>
>> http://datatracker.ietf.org/doc/draft-taylor-pim-v4v6-translation/
>
>The latter is very clear in saying
>
>   If an IPv6
>   group address to be translated matches the format specified in that
>   document for an IPv4-embedded IPv6 ASM or SSM group address, the
>   corresponding IPv4 group address MUST be obtained by extracting the
>   low-order 32 bits from the IPv6 address.  (The value of the sub-
>   group-id field is irrelevant to this procedure.)=20
>
>So that supports my conjecture that the following is a strong,=20
>unstated requirement on the format document:
>It MUST be possible to determine, by looking at a packet,=20
>whether the destination IP address in there is matching the=20
>format or not.
>
>This places an even stronger burden on the completeness of the=20
>specification than I initially thought.
>
>I would address this by describing the algorithm that gets=20
>used to determine whether there is a match by looking at the packet.
>(The fact that I cannot determine this algorithm even by=20
>educated guessing is my other main comment.)
>
>Gr=FC=DFe, Carsten
>
>=

From simon.perreault@viagenie.ca  Thu May 10 07:32:18 2012
Return-Path: <simon.perreault@viagenie.ca>
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 1DE7C21F8452; Thu, 10 May 2012 07:32:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-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 LduMU6MIEuto; Thu, 10 May 2012 07:32:14 -0700 (PDT)
Received: from jazz.viagenie.ca (unknown [IPv6:2620:0:230:8000:226:55ff:fe57:14db]) by ietfa.amsl.com (Postfix) with ESMTP id 6DA0221F867D; Thu, 10 May 2012 07:32:14 -0700 (PDT)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c000:708f:61db:4f9d:722f]) by jazz.viagenie.ca (Postfix) with ESMTPSA id ED2944159D; Thu, 10 May 2012 10:32:08 -0400 (EDT)
Message-ID: <4FABD168.2070802@viagenie.ca>
Date: Thu, 10 May 2012 10:32:08 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
References: <92309DC0-A179-4B5B-9D8C-4B55F64A4668@tzi.org> <94C682931C08B048B7A8645303FDC9F36E29946F71@PUEXCB1B.nanterre.francetelecom.fr> <9DBF9340-B04E-4A6A-98A1-B90525A1407C@tzi.org> <D003B142-55BA-4DD6-B293-849CB828E1E6@huawei.com> <C808362C-EA9A-4AC7-8CD0-19DC943DB02F@tzi.org>
In-Reply-To: <C808362C-EA9A-4AC7-8CD0-19DC943DB02F@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mboned@ietf.org" <mboned@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 10 May 2012 14:32:18 -0000

(Trimmed recipient list...)

On 2012-05-10 07:00, Carsten Bormann wrote:
>> http://datatracker.ietf.org/doc/draft-perreault-mboned-igmp-mld-translation/
>
> This document reveals that the IPv4 multicast address embedded into
> the IPv6 multicast address is indeed used as such by applications on
> the other side of the mapper (5.2.4). My main comment is that the
> mboned-64-multicast-address-format document does not even hint that
> this might be the case, much less defines semantics that might be
> used by an application on the IPv6 side (and there have been other
> comments that applications are not even involved on the IPv6 side,
> which doesn't quite seem to mesh with this document).

The intent is that applications will not need to know that a multicast 
address has been translated. No need to modify existing applications, 
and no need to change existing application development practices.

Two additional, entirely optional capabilities are offered to applications:

- Applications will be able to detect that an IPv6 multicast address 
contains an embedded IPv4 address by inspecting the special IPv6 prefix.

- Applications will be able to detect ICMPv3/MLDv2 messages that have 
been translated by inspecting the special "T" bit that is set by a 
translator.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From gjshep@gmail.com  Thu May 10 10:33:14 2012
Return-Path: <gjshep@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 D076211E809A for <mboned@ietfa.amsl.com>; Thu, 10 May 2012 10:33:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x4W0LHQtowiO for <mboned@ietfa.amsl.com>; Thu, 10 May 2012 10:33:14 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1037D11E808F for <mboned@ietf.org>; Thu, 10 May 2012 10:33:13 -0700 (PDT)
Received: by bkty8 with SMTP id y8so1780462bkt.31 for <mboned@ietf.org>; Thu, 10 May 2012 10:33:13 -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=6Va3+oLV0BGTHRx03QY7zR0WupUtpD+J/q0D8msMpyk=; b=cvxqOlOhXgtH9u5bpqJy2DDndDQ/mmt7YxBMyvPEtyQABvuNLLScrwbB0BxERksdfa RtNJvdn3JmLeNR2JqEiyAgvdzZ7YeIdLIPk905lFUTr/0hD28+LhfQDNLdFM3Gr7Vr/F Q32MGBhZIu2OypsJ6kpGsVCN4tCzcLk4HelGBI/kP0bJr8OYzza6XcnokestKmAFMHEi hxrdMFnCzcoBsItvKC03lBrsQiLbTIpuyznE3VhDbC2qKhiOuZbBQhgGWdAwH+0t5Kjd RRWDMc+lrbMwInX184xjs3zKSqCAPwK+fHJYKHNWc6Errp+1hV08vs+p/gN4jkHaZGyn W+cQ==
MIME-Version: 1.0
Received: by 10.205.119.130 with SMTP id fu2mr3168733bkc.120.1336671193123; Thu, 10 May 2012 10:33:13 -0700 (PDT)
Received: by 10.205.35.2 with HTTP; Thu, 10 May 2012 10:33:13 -0700 (PDT)
Date: Thu, 10 May 2012 10:33:13 -0700
Message-ID: <CABFReBqo43QsBWwu=_nbDgw-eoK1S2+8xszTXY1Zm=KLhmvRPA@mail.gmail.com>
From: Greg Shepherd <gjshep@gmail.com>
To: mboned@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gjshep@gmail.com
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, 10 May 2012 17:33:14 -0000

*,

Yes, I think we may finally be here! The Paris and post-Paris
discussions were addressed in the finally rev so it is now time for
WGLC for draft-ietf-mboned-auto-multicast-13:

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

It is quite long so we'll give it three weeks for responses before
moving it along. Please respond by May 31st. And as always, we need
votes of approval as much as comments and issues. Let's see this
finally move to req pub!

Thanks to everyone who has been involved throughout the past +decade. :p

MBONED Chairs

From Tina.Tsou.Zouting@huawei.com  Thu May 10 10:50:12 2012
Return-Path: <Tina.Tsou.Zouting@huawei.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 BB59A21F86EF for <mboned@ietfa.amsl.com>; Thu, 10 May 2012 10:50:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.48
X-Spam-Level: 
X-Spam-Status: No, score=-2.48 tagged_above=-999 required=5 tests=[AWL=0.118,  BAYES_00=-2.599, HTML_MESSAGE=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 pUUOwmJ3OYqE for <mboned@ietfa.amsl.com>; Thu, 10 May 2012 10:50:10 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id A049221F86DD for <mboned@ietf.org>; Thu, 10 May 2012 10:50:05 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFT73517; Thu, 10 May 2012 13:50:05 -0400 (EDT)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 10 May 2012 10:49:19 -0700
Received: from SZXEML420-HUB.china.huawei.com (10.82.67.159) by dfweml406-hub.china.huawei.com (10.193.5.131) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 10 May 2012 10:49:25 -0700
Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.48]) by szxeml420-hub.china.huawei.com ([10.82.67.159]) with mapi id 14.01.0323.003; Fri, 11 May 2012 01:49:19 +0800
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Leonard Giuliano <lenny@juniper.net>, Greg Shepherd <gjshep@gmail.com>
Thread-Topic: draft-tsou-mboned-multrans-addr-acquisition-01
Thread-Index: Ac0olW4tpAJfzZWwTw2lKRKI4vlTgAGPwEow
Date: Thu, 10 May 2012 17:49:19 +0000
Message-ID: <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.212.245.76]
Content-Type: multipart/alternative; boundary="_000_C0E0A32284495243BDE0AC8A066631A80C9CCCCEszxeml526mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "'mboned@ietf.org'" <mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 10 May 2012 17:50:12 -0000

--_000_C0E0A32284495243BDE0AC8A066631A80C9CCCCEszxeml526mbschi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear chairs,
Would you ask the WG for adoption of draft-tsou-mboned-multrans-addr-acquis=
ition-01 as WG document?

Thank you and have a good day.

Tina and co-authors

From: Tina TSOU
Sent: Wednesday, May 02, 2012 11:58 AM
To: mboned@ietf.org
Subject: draft-tsou-mboned-multrans-addr-acquisition-01


Now that the multicast transition framework document is officially accepted=
, is the Working Group prepared also to take on the topic of address acquis=
ition, which is one of the tasks it identifies?
If so, would draft-tsou-mboned-multrans-addr-acquisition-01 be acceptable a=
s a starting point?

Tina


--_000_C0E0A32284495243BDE0AC8A066631A80C9CCCCEszxeml526mbschi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Dear chairs,<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Would you ask the WG f=
or adoption of draft-tsou-mboned-multrans-addr-acquisition-01 as WG documen=
t?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thank you and have a g=
ood day.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Tina and co-authors<o:=
p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Tina TSO=
U
<br>
<b>Sent:</b> Wednesday, May 02, 2012 11:58 AM<br>
<b>To:</b> mboned@ietf.org<br>
<b>Subject:</b> draft-tsou-mboned-multrans-addr-acquisition-01<o:p></o:p></=
span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Now that the multicast transition framework docum=
ent is officially accepted, is the Working Group prepared also to take on t=
he topic of address acquisition, which is one of the tasks it identifies?<o=
:p></o:p></p>
<p class=3D"MsoNormal">If so, would draft-tsou-mboned-multrans-addr-acquisi=
tion-01 be acceptable as a starting point?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Tina<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_C0E0A32284495243BDE0AC8A066631A80C9CCCCEszxeml526mbschi_--

From brian@innovationslab.net  Thu May 10 11:03:12 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 0723221F86C8; Thu, 10 May 2012 11:03:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.766
X-Spam-Level: 
X-Spam-Status: No, score=-102.766 tagged_above=-999 required=5 tests=[AWL=-0.167, 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 rST6TjBbhHHQ; Thu, 10 May 2012 11:03:08 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2D54521F86C6; Thu, 10 May 2012 11:03:08 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 1566B88116; Thu, 10 May 2012 11:03:08 -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 3DAD3140039; Thu, 10 May 2012 11:03:07 -0700 (PDT)
Message-ID: <4FAC02D9.1050301@innovationslab.net>
Date: Thu, 10 May 2012 14:03:05 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
References: <CBD0A398.20BF2%yiu_lee@cable.comcast.com>
In-Reply-To: <CBD0A398.20BF2%yiu_lee@cable.comcast.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "6man@ietf.org" <6man@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>, The IESG <iesg@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 10 May 2012 18:03:12 -0000

Hi Yiu,
      Let me ask a few questions...

On 5/9/12 10:52 PM, Lee, Yiu wrote:
> Hi Carsten,
>
> Thanks very much for reviewing the document. I just want to add a point to
> your question about how applications decide when to use this multicast
> address format. In fact, they don't. Imagine a use case where a legacy
> IPv4 IP-TV receiver (an app) wants to join a channel which is broadcasted
> in IPv6. The app will continue to send the igmp-join (say 224.1.2.3).

How does the IPv4 IP-TV know to join 224.1.2.3?

How is 224.1.2.3 advertised to the IPv4 IP-TV clients if the content is 
generated by an IPv6 source?  Does the source need to be configured to 
use one of these IPv4-in-IPv6 multicast addresses?

> There will be a function in the network which is statically configured
> that when it receives a igmp-join, it would covert to a corresponding
> mld-join. The IPv6 address in the join message will follow what is
> described in this draft. This Adaptive Function is transparent to the
> application and managed by the network.

Are you limiting this approach to only mapping at the IGMP/MLD protocols?

How does your Adaptive Function know which IPv6 multicast prefix to use 
when mapping the IPv4 multicast address in the IGMP Report message to MLD?

Regards,
Brian

From albert.e.manfredi@boeing.com  Thu May 10 14:07:11 2012
Return-Path: <albert.e.manfredi@boeing.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 C6D4021F85EE; Thu, 10 May 2012 14:07:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.339
X-Spam-Level: 
X-Spam-Status: No, score=-5.339 tagged_above=-999 required=5 tests=[AWL=-2.740, BAYES_00=-2.599]
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 2ZUGpa6bBJwo; Thu, 10 May 2012 14:07:11 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 280AC21F85EA; Thu, 10 May 2012 14:07:11 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id q4AL76O5023124; Thu, 10 May 2012 14:07:06 -0700
Received: from blv-av-01.boeing.com (blv-av-01.ns.cs.boeing.com [130.247.48.231]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id q4AL73TI023105 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 10 May 2012 14:07:04 -0700
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id q4AL77h4008319; Thu, 10 May 2012 14:07:07 -0700 (PDT)
Received: from XCH-MWHT-06.mw.nos.boeing.com (xch-mwht-06.mw.nos.boeing.com [134.57.113.166]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q4AL77CR008249 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 10 May 2012 14:07:07 -0700 (PDT)
Received: from XCH-MW-08V.mw.nos.boeing.com ([134.57.119.191]) by XCH-MWHT-06.mw.nos.boeing.com ([134.57.113.166]) with mapi; Thu, 10 May 2012 16:07:07 -0500
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Brian Haberman <brian@innovationslab.net>
Date: Thu, 10 May 2012 16:07:05 -0500
Thread-Topic: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
Thread-Index: Ac0u1y3MdTQ8TDpqSpiBmAH1uueWYQAGMaDQ
Message-ID: <B0147C3DD45E42478038FC347CCB65FE02BB8BB3B8@XCH-MW-08V.mw.nos.boeing.com>
References: <CBD0A398.20BF2%yiu_lee@cable.comcast.com> <4FAC02D9.1050301@innovationslab.net>
In-Reply-To: <4FAC02D9.1050301@innovationslab.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
X-TM-AS-MML: No
Cc: "mboned@ietf.org" <mboned@ietf.org>, "6man@ietf.org" <6man@ietf.org>, The IESG <iesg@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>
Subject: Re: [MBONED] APPSDIR review of	draft-ietf-mboned-64-multicast-address-format-01
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, 10 May 2012 21:07:11 -0000

> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On
> Behalf Of Brian Haberman

> On 5/9/12 10:52 PM, Lee, Yiu wrote:
> > Hi Carsten,
> >
> > Thanks very much for reviewing the document. I just want to add a
> point to
> > your question about how applications decide when to use this
> multicast
> > address format. In fact, they don't. Imagine a use case where a
> legacy
> > IPv4 IP-TV receiver (an app) wants to join a channel which is
> broadcasted
> > in IPv6. The app will continue to send the igmp-join (say 224.1.2.3).
>=20
> How does the IPv4 IP-TV know to join 224.1.2.3?

My suggested answers would be:

The IP-TV server provider's EPG web site provides the IP-TV with the multic=
ast group address.

> How is 224.1.2.3 advertised to the IPv4 IP-TV clients if the content is
> generated by an IPv6 source?  Does the source need to be configured to
> use one of these IPv4-in-IPv6 multicast addresses?

The EPG web server detects that the client IP-TV is using IPv4, so it provi=
des the IPv4 address.

> > There will be a function in the network which is statically
> configured
> > that when it receives a igmp-join, it would covert to a corresponding
> > mld-join. The IPv6 address in the join message will follow what is
> > described in this draft. This Adaptive Function is transparent to the
> > application and managed by the network.
>=20
> Are you limiting this approach to only mapping at the IGMP/MLD
> protocols?
>=20
> How does your Adaptive Function know which IPv6 multicast prefix to use
> when mapping the IPv4 multicast address in the IGMP Report message to
> MLD?

This has to be table lookup. The IPv6 prefix for these IPv4 multicast group=
s is always the same, or the service provider has a table that specifies th=
e IPv6 prefix for use with each IPv4 group.

Bert


From Tina.Tsou.Zouting@huawei.com  Thu May 10 17:04:09 2012
Return-Path: <Tina.Tsou.Zouting@huawei.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 5FC3E21F85D5; Thu, 10 May 2012 17:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level: 
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.115,  BAYES_00=-2.599]
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 mmSj-cNTUGlE; Thu, 10 May 2012 17:04:02 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 86EEC21F8540; Thu, 10 May 2012 17:04:02 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFT93314; Thu, 10 May 2012 20:04:02 -0400 (EDT)
Received: from DFWEML403-HUB.china.huawei.com (10.193.5.151) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 10 May 2012 17:01:53 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.80]) by dfweml403-hub.china.huawei.com ([10.193.5.151]) with mapi id 14.01.0323.003; Thu, 10 May 2012 17:01:54 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Brian Haberman <brian@innovationslab.net>, "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
Thread-Topic: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
Thread-Index: AQHNLvGKIAZQ60ycT0KRymA2IFYsKpbEKgCw
Date: Fri, 11 May 2012 00:01:53 +0000
Message-ID: <C0E0A32284495243BDE0AC8A066631A80D37725C@dfweml513-mbx.china.huawei.com>
References: <CBD0A398.20BF2%yiu_lee@cable.comcast.com> <4FAC02D9.1050301@innovationslab.net>
In-Reply-To: <4FAC02D9.1050301@innovationslab.net>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.212.245.24]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "mboned@ietf.org" <mboned@ietf.org>, "6man@ietf.org" <6man@ietf.org>, The IESG <iesg@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>
Subject: Re: [MBONED] APPSDIR review of	draft-ietf-mboned-64-multicast-address-format-01
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, 11 May 2012 00:04:09 -0000

Tina


> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf
> Of Brian Haberman
> Sent: Thursday, May 10, 2012 11:03 AM
> To: Lee, Yiu
> Cc: 6man@ietf.org; apps-discuss@ietf.org application-layer protocols;
> draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org; The IES=
G;
> mboned@ietf.org
> Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-
> address-format-01
>=20
> Hi Yiu,
>       Let me ask a few questions...
>=20
> On 5/9/12 10:52 PM, Lee, Yiu wrote:
> > Hi Carsten,
> >
> > Thanks very much for reviewing the document. I just want to add a point
> to
> > your question about how applications decide when to use this multicast
> > address format. In fact, they don't. Imagine a use case where a legacy
> > IPv4 IP-TV receiver (an app) wants to join a channel which is
> broadcasted
> > in IPv6. The app will continue to send the igmp-join (say 224.1.2.3).
>=20
> How does the IPv4 IP-TV know to join 224.1.2.3?
>=20
> How is 224.1.2.3 advertised to the IPv4 IP-TV clients if the content is
> generated by an IPv6 source?  Does the source need to be configured to
> use one of these IPv4-in-IPv6 multicast addresses?
http://datatracker.ietf.org/doc/draft-tsou-mboned-multrans-addr-acquisition=
/
Hope it helps.
>=20
> > There will be a function in the network which is statically configured
> > that when it receives a igmp-join, it would covert to a corresponding
> > mld-join. The IPv6 address in the join message will follow what is
> > described in this draft. This Adaptive Function is transparent to the
> > application and managed by the network.
>=20
> Are you limiting this approach to only mapping at the IGMP/MLD protocols?
>=20
> How does your Adaptive Function know which IPv6 multicast prefix to use
> when mapping the IPv4 multicast address in the IGMP Report message to MLD=
?
>=20
> Regards,
> Brian
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From mohamed.boucadair@orange.com  Thu May 10 23:41: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 B625B21F85C7; Thu, 10 May 2012 23:41:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[AWL=0.148, 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 p+7xgwLZsboP; Thu, 10 May 2012 23:41:50 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id DE33F21F8504; Thu, 10 May 2012 23:41:49 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 0F6BB3B42F4; Fri, 11 May 2012 08:41:48 +0200 (CEST)
Received: from puexch31.nanterre.francetelecom.fr (unknown [10.101.44.29]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id DFB3335C05A; Fri, 11 May 2012 08:41:47 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by puexch31.nanterre.francetelecom.fr ([10.101.44.29]) with mapi; Fri, 11 May 2012 08:41:47 +0200
From: <mohamed.boucadair@orange.com>
To: Brian Haberman <brian@innovationslab.net>, "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
Date: Fri, 11 May 2012 08:41:46 +0200
Thread-Topic: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
Thread-Index: Ac0u1ylbb6PYrpP+Shu5SiZ9UsuKCgAZ/sdA
Message-ID: <94C682931C08B048B7A8645303FDC9F36E2A52C948@PUEXCB1B.nanterre.francetelecom.fr>
References: <CBD0A398.20BF2%yiu_lee@cable.comcast.com> <4FAC02D9.1050301@innovationslab.net>
In-Reply-To: <4FAC02D9.1050301@innovationslab.net>
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.5.11.4230
Cc: "6man@ietf.org" <6man@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>, The IESG <iesg@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 11 May 2012 06:41:50 -0000

Dear Brian,

Please see inline.

Cheers,
Med=20

>-----Message d'origine-----
>De : Brian Haberman [mailto:brian@innovationslab.net]=20
>Envoy=E9 : jeudi 10 mai 2012 20:03
>=C0 : Lee, Yiu
>Cc : Carsten Bormann; BOUCADAIR Mohamed OLNC/NAD/TIP;=20
>mboned@ietf.org; 6man@ietf.org; The IESG;=20
>apps-discuss@ietf.org application-layer protocols;=20
>draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org
>Objet : Re: [MBONED] APPSDIR review of=20
>draft-ietf-mboned-64-multicast-address-format-01
>
>Hi Yiu,
>      Let me ask a few questions...
>
>On 5/9/12 10:52 PM, Lee, Yiu wrote:
>> Hi Carsten,
>>
>> Thanks very much for reviewing the document. I just want to=20
>add a point to
>> your question about how applications decide when to use this=20
>multicast
>> address format. In fact, they don't. Imagine a use case=20
>where a legacy
>> IPv4 IP-TV receiver (an app) wants to join a channel which=20
>is broadcasted
>> in IPv6. The app will continue to send the igmp-join (say 224.1.2.3).
>
>How does the IPv4 IP-TV know to join 224.1.2.3?

Med: For this particular case (i.e., IPv4-only receiver over an IPv6 networ=
k+IPv4 source), the same discovery mechanism as for an IPv4-only network wi=
ll be used.=20

>
>How is 224.1.2.3 advertised to the IPv4 IP-TV clients if the=20
>content is=20
>generated by an IPv6 source?=20

Med: The source is IPv4 but the IPv4-enabled receiver is connected to an IP=
v6-only network (e.g., http://tools.ietf.org/html/draft-ietf-softwire-dslit=
e-multicast-02#section-4).

 Does the source need to be configured to=20
>use one of these IPv4-in-IPv6 multicast addresses?

Med: This address is an address representing the IPv4 source in an IPv6 net=
work. The source is not required to be aware of that address.

>
>> There will be a function in the network which is statically=20
>configured
>> that when it receives a igmp-join, it would covert to a corresponding
>> mld-join. The IPv6 address in the join message will follow what is
>> described in this draft. This Adaptive Function is transparent to the
>> application and managed by the network.
>
>Are you limiting this approach to only mapping at the IGMP/MLD=20
>protocols?

Med: No. If the receiver is IPv6-enabled, it can build an IPv4-embedded IPv=
6 address if it has been configured with an MPREFIX64.

>
>How does your Adaptive Function know which IPv6 multicast=20
>prefix to use=20
>when mapping the IPv4 multicast address in the IGMP Report=20
>message to MLD?

Med: By configuration. Please refer to Section 6 of address format draft or=
 http://tools.ietf.org/html/draft-ietf-softwire-dslite-multicast-02#section=
-5.


>
>Regards,
>Brian
>=

From internet-drafts@ietf.org  Fri May 11 10:02:09 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 1386D21F867E; Fri, 11 May 2012 10:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.426
X-Spam-Level: 
X-Spam-Status: No, score=-102.426 tagged_above=-999 required=5 tests=[AWL=0.173, 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 rly-w8oxtL6t; Fri, 11 May 2012 10:02:08 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94F8721F859E; Fri, 11 May 2012 10:02: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.02
Message-ID: <20120511170208.31690.74168.idtracker@ietfa.amsl.com>
Date: Fri, 11 May 2012 10:02:08 -0700
Cc: mboned@ietf.org
Subject: [MBONED] I-D Action: draft-ietf-mboned-v4v6-mcast-ps-00.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, 11 May 2012 17:02:09 -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=
 IETF.

	Title           : IPv4-IPv6 Multicast: Problem Statement and Use Cases
	Author(s)       : Christian Jacquenet
                          Mohamed Boucadair
                          Yiu Lee
                          Jacni Qin
                          Tina Tsou
                          Qiong Sun
	Filename        : draft-ietf-mboned-v4v6-mcast-ps-00.txt
	Pages           : 25
	Date            : 2012-05-11

   This document discusses issues and requirements raised by IPv4-IPv6
   multicast interconnection and co-existence scenarios.  It also
   discusses various multicast use cases which may occur during IPv6
   transitioning.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mboned-v4v6-mcast-ps-00.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mboned-v4v6-mcast-ps-00.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-v4v6-mcast-ps/


From lenny@juniper.net  Mon May 14 13:24:53 2012
Return-Path: <lenny@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 D527D21F88AC for <mboned@ietfa.amsl.com>; Mon, 14 May 2012 13:24:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[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 hiORBUNIQsiq for <mboned@ietfa.amsl.com>; Mon, 14 May 2012 13:24:53 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id 3E95621F88AA for <mboned@ietf.org>; Mon, 14 May 2012 13:24:53 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKT7FqEwY4zns/nOCnkzoP88OKbXRQCorW@postini.com; Mon, 14 May 2012 13:24:53 PDT
Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB02-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 14 May 2012 13:24:33 -0700
Received: from eng-mail01.juniper.net (eng-mail01.juniper.net [172.17.28.114]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id q4EKOO188087; Mon, 14 May 2012 13:24:32 -0700 (PDT)	(envelope-from lenny@juniper.net)
Received: by eng-mail01.juniper.net (Postfix, from userid 1709)	id 078A01144F;  Mon, 14 May 2012 13:24:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])	by eng-mail01.juniper.net (Postfix) with ESMTP id EFC5F1141B; Mon, 14 May 2012 13:24:23 -0700 (PDT)
Date: Mon, 14 May 2012 13:24:23 -0700
From: Leonard Giuliano <lenny@juniper.net>
To: MBONED WG <mboned@ietf.org>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com>
Message-ID: <20120514132102.U91557@eng-mail01.juniper.net>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 14 May 2012 20:24:53 -0000

We would like to poll the WG to decide if 
draft-tsou-mboned-multrans-addr-acquisition-01 should be adopted as an 
MBONED document.  Please respnd by May 29 if you thing this doc should or 
should not be adopted by MBONED.


-MBONED Chairs


On Thu, 10 May 2012, Tina TSOU wrote:

-) Dear chairs,
-) Would you ask the WG for adoption of draft-tsou-mboned-multrans-addr-acquisition-01 as WG document?
-) 
-) Thank you and have a good day.
-) 
-) Tina and co-authors
-) 
-) From: Tina TSOU
-) Sent: Wednesday, May 02, 2012 11:58 AM
-) To: mboned@ietf.org
-) Subject: draft-tsou-mboned-multrans-addr-acquisition-01
-) 
-) 
-) Now that the multicast transition framework document is officially accepted, is the Working Group prepared also to take on the topic of address acquisition, which is one of the tasks it identifies?
-) If so, would draft-tsou-mboned-multrans-addr-acquisition-01 be acceptable as a starting point?
-) 
-) Tina
-) 
-) 

From yiu_lee@cable.comcast.com  Mon May 14 13:50:09 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 9DADA21F8874; Mon, 14 May 2012 13:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.889
X-Spam-Level: 
X-Spam-Status: No, score=-102.889 tagged_above=-999 required=5 tests=[AWL=2.342, 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 OfPIo8n0CVJx; Mon, 14 May 2012 13:50:09 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 9C5E521F8851; Mon, 14 May 2012 13:50:08 -0700 (PDT)
Received: from ([24.40.56.115]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.17273847; Mon, 14 May 2012 14:35:14 -0600
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0283.003; Mon, 14 May 2012 16:50:05 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Brian Haberman <brian@innovationslab.net>
Thread-Topic: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
Thread-Index: AQHNMhMj+U0VWu2r9ka0j7sgZj2IEA==
Date: Mon, 14 May 2012 20:50:05 +0000
Message-ID: <CBD6E6C4.20E89%yiu_lee@cable.comcast.com>
In-Reply-To: <4FAC02D9.1050301@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.2.120421
x-originating-ip: [24.40.55.73]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3419859004_1695367"
MIME-Version: 1.0
Cc: "6man@ietf.org" <6man@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>, The IESG <iesg@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 14 May 2012 20:50:09 -0000

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

Hi Brian,

Sorry for getting back late. I read Bert's answers to your questions. His
answers are inline with my answers. Most information are statically
configured. For example: Ch1 is statically configured to 224.1.2.3 via OOB
mechanism. If the STB is IPv4 only, it will only use IPv4 mcast address.
It won't use the address format defined in this draft. In my mind, the
most common deployment will use the same IPv6 prefix which will be
statically configured in the AF.

Regards,
Yiu 


On 5/10/12 2:03 PM, "Brian Haberman" <brian@innovationslab.net> wrote:

>Hi Yiu,
>      Let me ask a few questions...
>
>On 5/9/12 10:52 PM, Lee, Yiu wrote:
>> Hi Carsten,
>>
>> Thanks very much for reviewing the document. I just want to add a point
>>to
>> your question about how applications decide when to use this multicast
>> address format. In fact, they don't. Imagine a use case where a legacy
>> IPv4 IP-TV receiver (an app) wants to join a channel which is
>>broadcasted
>> in IPv6. The app will continue to send the igmp-join (say 224.1.2.3).
>
>How does the IPv4 IP-TV know to join 224.1.2.3?
>
>How is 224.1.2.3 advertised to the IPv4 IP-TV clients if the content is
>generated by an IPv6 source?  Does the source need to be configured to
>use one of these IPv4-in-IPv6 multicast addresses?
>
>> There will be a function in the network which is statically configured
>> that when it receives a igmp-join, it would covert to a corresponding
>> mld-join. The IPv6 address in the join message will follow what is
>> described in this draft. This Adaptive Function is transparent to the
>> application and managed by the network.
>
>Are you limiting this approach to only mapping at the IGMP/MLD protocols?
>
>How does your Adaptive Function know which IPv6 multicast prefix to use
>when mapping the IPv4 multicast address in the IGMP Report message to MLD?
>
>Regards,
>Brian

--B_3419859004_1695367
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
Q0ECEFObm9wZOtwg92e9VN7esOQwCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJBDEWBBThgedx
5DPuPg/hVhQF9bK3GHAPgjAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ
BTEPFw0xMjA1MTQyMDUwMDNaMA0GCSqGSIb3DQEBAQUABIIBAInS7Nx19pik0LuaDeJRJk/j
YV2dTIe9e4YGGFLXxkaV+ESwC6ybtCtrcsFj4UB74368aHBZSqjn77h4JqkCkNl247krlWqn
qV9kY8m04PISu13l6zJRwXEdovfcRqENdqHYoIXXSH44oEfZUpWe4oBqkWTtJ4CKCaWjRXAw
u3gEzXOfAbqkNN8X3ya+GSdIkR9Sd3wuFJp03kyVHkjU8Zg3QMQNWJnBBC4MPQa2Nr/mmu5n
uHAdGhyK5XMDpXTsXP6jO6tWvs6SLxjF44SB7bmxKHQioOOd6UrZEUoihKsepBQm/2U4jNnu
Szx+t1nvATkdAgvwiFJWpCvOHjMnPqs=

--B_3419859004_1695367--

From yiu_lee@cable.comcast.com  Mon May 14 13:56:01 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 BF43A21F88AA for <mboned@ietfa.amsl.com>; Mon, 14 May 2012 13:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.337
X-Spam-Level: 
X-Spam-Status: No, score=-102.337 tagged_above=-999 required=5 tests=[AWL=1.497, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, 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 iyngYAf6-T4S for <mboned@ietfa.amsl.com>; Mon, 14 May 2012 13:56:01 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 0D85721F88A3 for <mboned@ietf.org>; Mon, 14 May 2012 13:56:00 -0700 (PDT)
Received: from ([24.40.56.115]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.17274917; Mon, 14 May 2012 14:40:48 -0600
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0283.003; Mon, 14 May 2012 16:55:46 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
Thread-Topic: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
Thread-Index: AQHNMhPunU9YqPyt7UyHMPQq+TIt2w==
Date: Mon, 14 May 2012 20:55:45 +0000
Message-ID: <CBD6E91D.20E97%yiu_lee@cable.comcast.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.2.120421
x-originating-ip: [24.40.55.73]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3419859345_1748567"
MIME-Version: 1.0
To: Tina TSOU <tina.tsou.zouting@huawei.com>, Leonard Giuliano <lenny@juniper.net>, Greg Shepherd <gjshep@gmail.com>
Cc: "'mboned@ietf.org'" <mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 14 May 2012 20:56:01 -0000

--B_3419859345_1748567
Content-type: multipart/alternative;
	boundary="B_3419859344_1755794"


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

Quick question to the authors. Why not the network preconfigure the IPv6
address from the v4 address and  give both IPv4 and IPv6 addresses to the
receivers and let the endpoint choose?

From:  Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Date:  Thursday, May 10, 2012 1:49 PM
To:  Leonard Giuliano <lenny@juniper.net>, Greg Shepherd <gjshep@gmail.com>
Cc:  "'mboned@ietf.org'" <mboned@ietf.org>
Subject:  Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01

Dear chairs,
Would you ask the WG for adoption of
draft-tsou-mboned-multrans-addr-acquisition-01 as WG document?
 
Thank you and have a good day.
 

Tina and co-authors
 

From: Tina TSOU 
Sent: Wednesday, May 02, 2012 11:58 AM
To: mboned@ietf.org
Subject: draft-tsou-mboned-multrans-addr-acquisition-01
 
Now that the multicast transition framework document is officially accepted,
is the Working Group prepared also to take on the topic of address
acquisition, which is one of the tasks it identifies?
If so, would draft-tsou-mboned-multrans-addr-acquisition-01 be acceptable as
a starting point?
 
Tina
 



--B_3419859344_1755794
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif; "><div>Quick question to the author=
s. Why not the network preconfigure the IPv6 address from the v4 address and=
 &nbsp;give both IPv4 and IPv6 addresses to the receivers and let the endpoi=
nt choose?&nbsp;</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><div st=
yle=3D"font-family:Calibri; font-size:11pt; text-align:left; color:black; BORD=
ER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDI=
NG-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGH=
T: medium none; PADDING-TOP: 3pt"><span style=3D"font-weight:bold">From: </spa=
n> Tina TSOU &lt;<a href=3D"mailto:Tina.Tsou.Zouting@huawei.com">Tina.Tsou.Zou=
ting@huawei.com</a>&gt;<br><span style=3D"font-weight:bold">Date: </span> Thur=
sday, May 10, 2012 1:49 PM<br><span style=3D"font-weight:bold">To: </span> Leo=
nard Giuliano &lt;<a href=3D"mailto:lenny@juniper.net">lenny@juniper.net</a>&g=
t;, Greg Shepherd &lt;<a href=3D"mailto:gjshep@gmail.com">gjshep@gmail.com</a>=
&gt;<br><span style=3D"font-weight:bold">Cc: </span> "<a href=3D"mailto:'mboned@=
ietf.org">'mboned@ietf.org</a>'" &lt;<a href=3D"mailto:mboned@ietf.org">mboned=
@ietf.org</a>&gt;<br><span style=3D"font-weight:bold">Subject: </span> Re: [MB=
ONED] draft-tsou-mboned-multrans-addr-acquisition-01<br></div><div><br></div=
><div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-microsoft=
-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" xmlns:x=3D=
"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-microsoft-com:=
office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office:access" xmlns:d=
t=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"uuid:BDC6E3F0-6DA3-11=
d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#=
RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" xmlns:ss=3D=
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c=3D"urn:schemas-microsof=
t-com:office:component:spreadsheet" xmlns:odc=3D"urn:schemas-microsoft-com:off=
ice:odc" xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" xmlns:html=3D"=
http://www.w3.org/TR/REC-html40" xmlns:q=3D"http://schemas.xmlsoap.org/soap/en=
velope/" xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" xmlns:d=3D"DA=
V:" xmlns:repl=3D"http://schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas=
.microsoft.com/sharepoint/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft=
.com/office/excel/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xs=
d" xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"=
http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://ww=
w.w3.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoin=
t/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http://w=
ww.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sharepoint=
/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" xmlns:sp=3D=
"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://schemas.microso=
ft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instanc=
e" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf=3D"http=
://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p=3D"http://schemas.micr=
osoft.com/data/udc/parttopart" xmlns:wf=3D"http://schemas.microsoft.com/sharep=
oint/soap/workflow/" xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/di=
gsig-setup" xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" xml=
ns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-signature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006" xml=
ns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels=3D"http://=
schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp=3D"http://mi=
crosoft.com/sharepoint/webpartpages" xmlns:ex12t=3D"http://schemas.microsoft.c=
om/exchange/services/2006/types" xmlns:ex12m=3D"http://schemas.microsoft.com/e=
xchange/services/2006/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sh=
arepoint/soap/SlideLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/Sh=
arePointPortalServer/PublishedLinksService" xmlns:st=3D"=01" xmlns=3D"http://www.w=
3.org/TR/REC-html40"><meta http-equiv=3D"Content-Type" content=3D"text/html; cha=
rset=3Dutf-8"><meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medi=
um)"><style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--><div lang=3D"EN-US" link=3D"blue" vlink=3D"purp=
le"><div class=3D"WordSection1"><p class=3D"MsoNormal"><span style=3D"color:#1F497=
D">Dear chairs,<o:p></o:p></span></p><p class=3D"MsoNormal"><span style=3D"color=
:#1F497D">Would you ask the WG for adoption of draft-tsou-mboned-multrans-ad=
dr-acquisition-01 as WG document?<o:p></o:p></span></p><p class=3D"MsoNormal">=
<span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p><p class=3D"MsoNormal"=
><span style=3D"color:#1F497D">Thank you and have a good day.<o:p></o:p></span=
></p><p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p><div><p class=3D"MsoNormal"><span style=3D"color:#1F497D">Tina and co-auth=
ors<o:p></o:p></span></p></div><p class=3D"MsoNormal"><span style=3D"color:#1F49=
7D"><o:p>&nbsp;</o:p></span></p><div style=3D"border:none;border-left:solid bl=
ue 1.5pt;padding:0in 0in 0in 4.0pt"><div><div style=3D"border:none;border-top:=
solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class=3D"MsoNormal"><b><span=
 style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b>=
<span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; "> Tina TSOU
<br><b>Sent:</b> Wednesday, May 02, 2012 11:58 AM<br><b>To:</b> <a href=3D"ma=
ilto:mboned@ietf.org">mboned@ietf.org</a><br><b>Subject:</b> draft-tsou-mbon=
ed-multrans-addr-acquisition-01<o:p></o:p></span></p></div></div><p class=3D"M=
soNormal"><o:p>&nbsp;</o:p></p><p class=3D"MsoPlainText">Now that the multicas=
t transition framework document is officially accepted, is the Working Group=
 prepared also to take on the topic of address acquisition, which is one of =
the tasks it identifies?<o:p></o:p></p><p class=3D"MsoNormal">If so, would dra=
ft-tsou-mboned-multrans-addr-acquisition-01 be acceptable as a starting poin=
t?<o:p></o:p></p><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p><p class=3D"MsoNorm=
al">Tina<o:p></o:p></p><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p></div></div=
></div></div></span></body></html>

--B_3419859344_1755794--

--B_3419859345_1748567
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
Q0ECEFObm9wZOtwg92e9VN7esOQwCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJBDEWBBQ1F00i
Zk4/VKWp+muSfahjO9T3DjAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ
BTEPFw0xMjA1MTQyMDU1NDRaMA0GCSqGSIb3DQEBAQUABIIBAAh+yYCtEO1Ff/XPODA2Fj6U
QsY0TaR6ReylwOAWfFaOz3zbQzX7Fn86nJltb3K6qKlnSmK3JDaeIjfhBzJDOLP0JoIqLuO0
6pmqcGazKme8INI4g+6Vwm15fl3QXiQvyFRWEAjI0AEXDF/z45h/WqGY870EEFTNQQkuVRU3
5GjOUf289jV5mp2EndxxLig4XDjycTRlhrD0WBhNdtQWvy+kRv2jU3nvkGwd3shBLCN1DlIB
H4KLeP52yOzFIhgfzBAFiZcB56hFufYRSzf+n5YdOb2h/vKqq9TmrCxlkZF7zDw1ZseNnYy0
oP+NJFiKK5LIK/PCdlsJp2Y2BOu8rLE=

--B_3419859345_1748567--

From stig@cisco.com  Mon May 14 13:56:17 2012
Return-Path: <stig@cisco.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 7534721F88D7; Mon, 14 May 2012 13:56:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.488
X-Spam-Level: 
X-Spam-Status: No, score=-10.488 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 Agf7vlPV5QTY; Mon, 14 May 2012 13:56:16 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id E1B6321F88D0; Mon, 14 May 2012 13:56:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stig@cisco.com; l=2436; q=dns/txt; s=iport; t=1337028976; x=1338238576; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=V1tSm+T2ut33g9eQbqN22VxboLXucE+8L6KoN0ebAgo=; b=YGKJANvw5LZKtyBqXzzLULi1TjeigsaKwZMJKCbLFNo0lKQAJH+WzTe9 11zkeOpe2GLqVV2gyDfbW5Wnj1UfsO0kFoqH4K5TqeGT4glOnxmxfc6v5 IK7AfNaQQSRaYrBMxjaXNDxtzvsaAeh6hcByQgR6a8RUgJmrjYs9mLlcd o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFACBwsU+rRDoI/2dsb2JhbABEgx6wVoEHghUBAQEDARIBJUABEAsYCRYPCQMCAQIBRQYNAQUCAQEeh2cEmwGfdIsahgAEiGSNGYV1iGKBaYMJ
X-IronPort-AV: E=Sophos;i="4.75,588,1330905600"; d="scan'208";a="44677530"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 14 May 2012 20:56:16 +0000
Received: from [10.154.208.109] ([10.154.208.109]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q4EKuGRW005062; Mon, 14 May 2012 20:56:16 GMT
Message-ID: <4FB17170.8090203@cisco.com>
Date: Mon, 14 May 2012 13:56:16 -0700
From: Stig Venaas <stig@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
References: <CBD6E6C4.20E89%yiu_lee@cable.comcast.com>
In-Reply-To: <CBD6E6C4.20E89%yiu_lee@cable.comcast.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "6man@ietf.org" <6man@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>, The IESG <iesg@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 14 May 2012 20:56:17 -0000

On 5/14/2012 1:50 PM, Lee, Yiu wrote:
> Hi Brian,
>
> Sorry for getting back late. I read Bert's answers to your questions. His
> answers are inline with my answers. Most information are statically
> configured. For example: Ch1 is statically configured to 224.1.2.3 via OOB
> mechanism. If the STB is IPv4 only, it will only use IPv4 mcast address.
> It won't use the address format defined in this draft. In my mind, the
> most common deployment will use the same IPv6 prefix which will be
> statically configured in the AF.

Right, so that was my main concern with the draft. Is static
configuration like this sufficient, or are there more generic cases
where one needs to know that it is translated from IPv4 without a
priori configuration. The flag bit (or a well-known prefix) is only
needed in the latter case. I know there were some scenarios where
someone found the latter to be advantageous though.

Stig

>
> Regards,
> Yiu
>
>
> On 5/10/12 2:03 PM, "Brian Haberman"<brian@innovationslab.net>  wrote:
>
>> Hi Yiu,
>>       Let me ask a few questions...
>>
>> On 5/9/12 10:52 PM, Lee, Yiu wrote:
>>> Hi Carsten,
>>>
>>> Thanks very much for reviewing the document. I just want to add a point
>>> to
>>> your question about how applications decide when to use this multicast
>>> address format. In fact, they don't. Imagine a use case where a legacy
>>> IPv4 IP-TV receiver (an app) wants to join a channel which is
>>> broadcasted
>>> in IPv6. The app will continue to send the igmp-join (say 224.1.2.3).
>>
>> How does the IPv4 IP-TV know to join 224.1.2.3?
>>
>> How is 224.1.2.3 advertised to the IPv4 IP-TV clients if the content is
>> generated by an IPv6 source?  Does the source need to be configured to
>> use one of these IPv4-in-IPv6 multicast addresses?
>>
>>> There will be a function in the network which is statically configured
>>> that when it receives a igmp-join, it would covert to a corresponding
>>> mld-join. The IPv6 address in the join message will follow what is
>>> described in this draft. This Adaptive Function is transparent to the
>>> application and managed by the network.
>>
>> Are you limiting this approach to only mapping at the IGMP/MLD protocols?
>>
>> How does your Adaptive Function know which IPv6 multicast prefix to use
>> when mapping the IPv4 multicast address in the IGMP Report message to MLD?
>>
>> Regards,
>> Brian


From yiu_lee@cable.comcast.com  Mon May 14 14:06:09 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 0964E21F88D7; Mon, 14 May 2012 14:06:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.957
X-Spam-Level: 
X-Spam-Status: No, score=-100.957 tagged_above=-999 required=5 tests=[AWL=-0.060, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, IP_NOT_FRIENDLY=0.334, 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 l40zxFKYPQba; Mon, 14 May 2012 14:06:08 -0700 (PDT)
Received: from cable.comcast.com (pacdcavout01.cable.comcast.com [69.241.43.119]) by ietfa.amsl.com (Postfix) with ESMTP id F40C821F88D0; Mon, 14 May 2012 14:06:07 -0700 (PDT)
Received: from ([24.40.56.115]) by pacdcavaout01.cable.comcast.com with ESMTP  id 97wm3m1.12433251; Mon, 14 May 2012 16:58:01 -0400
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0283.003; Mon, 14 May 2012 17:06:03 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Stig Venaas <stig@cisco.com>
Thread-Topic: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
Thread-Index: AQHNMhVebHEh+DeZCkG2+0xN2kXo1Q==
Date: Mon, 14 May 2012 21:06:02 +0000
Message-ID: <CBD6EB81.20E9E%yiu_lee@cable.comcast.com>
In-Reply-To: <4FB17170.8090203@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.2.120421
x-originating-ip: [24.40.55.71]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3419859958_1782930"
MIME-Version: 1.0
Cc: "6man@ietf.org" <6man@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>, The IESG <iesg@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 14 May 2012 21:06:09 -0000

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

Hi Stig,

Right. I explain only one use case. Other may find the latter case is more
attractive for their deployments. This address format should enable the
dynamic use case as well.

Yiu

On 5/14/12 4:56 PM, "Stig Venaas" <stig@cisco.com> wrote:

>On 5/14/2012 1:50 PM, Lee, Yiu wrote:
>> Hi Brian,
>>
>> Sorry for getting back late. I read Bert's answers to your questions.
>>His
>> answers are inline with my answers. Most information are statically
>> configured. For example: Ch1 is statically configured to 224.1.2.3 via
>>OOB
>> mechanism. If the STB is IPv4 only, it will only use IPv4 mcast address.
>> It won't use the address format defined in this draft. In my mind, the
>> most common deployment will use the same IPv6 prefix which will be
>> statically configured in the AF.
>
>Right, so that was my main concern with the draft. Is static
>configuration like this sufficient, or are there more generic cases
>where one needs to know that it is translated from IPv4 without a
>priori configuration. The flag bit (or a well-known prefix) is only
>needed in the latter case. I know there were some scenarios where
>someone found the latter to be advantageous though.
>
>Stig
>
>>
>> Regards,
>> Yiu
>>
>>
>> On 5/10/12 2:03 PM, "Brian Haberman"<brian@innovationslab.net>  wrote:
>>
>>> Hi Yiu,
>>>       Let me ask a few questions...
>>>
>>> On 5/9/12 10:52 PM, Lee, Yiu wrote:
>>>> Hi Carsten,
>>>>
>>>> Thanks very much for reviewing the document. I just want to add a
>>>>point
>>>> to
>>>> your question about how applications decide when to use this multicast
>>>> address format. In fact, they don't. Imagine a use case where a legacy
>>>> IPv4 IP-TV receiver (an app) wants to join a channel which is
>>>> broadcasted
>>>> in IPv6. The app will continue to send the igmp-join (say 224.1.2.3).
>>>
>>> How does the IPv4 IP-TV know to join 224.1.2.3?
>>>
>>> How is 224.1.2.3 advertised to the IPv4 IP-TV clients if the content is
>>> generated by an IPv6 source?  Does the source need to be configured to
>>> use one of these IPv4-in-IPv6 multicast addresses?
>>>
>>>> There will be a function in the network which is statically configured
>>>> that when it receives a igmp-join, it would covert to a corresponding
>>>> mld-join. The IPv6 address in the join message will follow what is
>>>> described in this draft. This Adaptive Function is transparent to the
>>>> application and managed by the network.
>>>
>>> Are you limiting this approach to only mapping at the IGMP/MLD
>>>protocols?
>>>
>>> How does your Adaptive Function know which IPv6 multicast prefix to use
>>> when mapping the IPv4 multicast address in the IGMP Report message to
>>>MLD?
>>>
>>> Regards,
>>> Brian
>

--B_3419859958_1782930
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
Q0ECEFObm9wZOtwg92e9VN7esOQwCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJBDEWBBTAq2zn
ZPeVlEQHgHaFnprZH0fIvjAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ
BTEPFw0xMjA1MTQyMTA1NTZaMA0GCSqGSIb3DQEBAQUABIIBAHdOIPKCSaqnDs54f/p82748
qS64Ty+gw/ev+sglJY16Leq4prlW/B47Eop43jf+/5yd/5FGrQQTxXHaJH8kBdCoVgaSZnbi
IOE+KcwBow0CXNXq44Nt84MEfKf2j4qSUFdT2fUHjIDhDKW5iZrw5PLbtJ+1qF0Py1Bt1lpY
GBuLfpPve8o3YkSjjKaPeakndgmH7LZtHm8aJyD0KbuhL3/iQXQdzV1m9ylxGriCKPAQ+tJf
mNPODHEFMFM1BMqSgahfvg/xEwjZQHMNpmsShOC8VovcYwlPM0J8uyL49+QCxt3Z/hnH7OHH
TCYkIf4uhyq+nB9LyvpKd0CB9mLlbPA=

--B_3419859958_1782930--

From tom.taylor.stds@gmail.com  Mon May 14 17:27:32 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 A485321F8892 for <mboned@ietfa.amsl.com>; Mon, 14 May 2012 17:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.475
X-Spam-Level: 
X-Spam-Status: No, score=-3.475 tagged_above=-999 required=5 tests=[AWL=0.124,  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 rR5Agti+PB+j for <mboned@ietfa.amsl.com>; Mon, 14 May 2012 17:27:31 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id F15A121F888B for <mboned@ietf.org>; Mon, 14 May 2012 17:27:30 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so4254382lbb.31 for <mboned@ietf.org>; Mon, 14 May 2012 17:27:29 -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=W/t0jiPn/re6Eq+OTucmn62sKu6FUk5S9l7PElcx5gM=; b=OLACdcIiFS5kYoQFf0qfUYoIPGojC1crc39iy4ZwvLVK9gChrSl+/zwmwHFSETy0rD zkiAPiDgcyNPSBu2+McipVkUgWG/VqTzuAmo2bXjQkfuLnlLDjDyHWV5biEQ72R4YtbO b26v8orbjice4OudQrLUtixZSxQUgLrotrKcb1GUb6sePQHazxYgXBEOcL0L6HAw0kN4 GdPHMtiry5kC9nhKdbKSnbRVk+kMxOAV87Ew0l/azEPucyf2hMglw772ZnKmQgzc7VxR 6hkvzTJ+o8y0CRlHv0XBY7PC6WbFOTdssds5iZeS9tRLC3HBamd0ZwhKHBPDmdpwHvd4 mhFw==
Received: by 10.112.48.195 with SMTP id o3mr4434157lbn.88.1337041649854; Mon, 14 May 2012 17:27:29 -0700 (PDT)
Received: from [127.0.0.1] (dsl-207-112-91-137.tor.primus.ca. [207.112.91.137]) by mx.google.com with ESMTPS id nv7sm21098364lab.9.2012.05.14.17.27.26 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 14 May 2012 17:27:28 -0700 (PDT)
Message-ID: <4FB1A2EB.1000001@gmail.com>
Date: Mon, 14 May 2012 20:27:23 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: mboned@ietf.org
References: <CBD6E91D.20E97%yiu_lee@cable.comcast.com>
In-Reply-To: <CBD6E91D.20E97%yiu_lee@cable.comcast.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120514-1, 14/05/2012), Outbound message
X-Antivirus-Status: Clean
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 15 May 2012 00:27:32 -0000

I believe that is the "administrative preparation" strategy described in 
the document.

Tom Taylor

On 14/05/2012 4:55 PM, Lee, Yiu wrote:
> Quick question to the authors. Why not the network preconfigure the IPv6
> address from the v4 address and  give both IPv4 and IPv6 addresses to the
> receivers and let the endpoint choose?
>
...

From jacni@jacni.com  Mon May 14 18:47:07 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 CCF7F21F892A for <mboned@ietfa.amsl.com>; Mon, 14 May 2012 18:47:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.886
X-Spam-Level: 
X-Spam-Status: No, score=-1.886 tagged_above=-999 required=5 tests=[AWL=0.401,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=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 rY36Pklaw8Xz for <mboned@ietfa.amsl.com>; Mon, 14 May 2012 18:47:07 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 54A1421F890B for <mboned@ietf.org>; Mon, 14 May 2012 18:47:06 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 6FFB43800BF for <mboned@ietf.org>; Mon, 14 May 2012 21:47:05 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with ESMTP id 6910134007A for <mboned@ietf.org>; Tue, 15 May 2012 09:47:03 +0800 (CST)
Received: from [10.140.20.37] (unknown [64.104.125.217]) by app (Coremail) with SMTP id +AWowJALoQKUtbFPY37zAA--.31134S2; Tue, 15 May 2012 09:47:01 +0800 (CST)
Message-ID: <4FB1B592.1090706@jacni.com>
Date: Tue, 15 May 2012 09:46:58 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------020609080100080207020505"
X-CM-TRANSID: +AWowJALoQKUtbFPY37zAA--.31134S2
X-Coremail-Antispam: 1UD129KBjvJXoW7AF17Aw4DuFykCFyrZF1xAFb_yoW8JFyxpa 17WayUKr4kJr4Iy3y8ZF1fKr1S9FyDJrW7JF98Kr1q9ay5XF18tw1Yy345tryUWrn5Aasr XF18uw1UXr43Z3JanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU7jb7Iv0xC_Cr1lb4IE77IF4wAFc2x0x2IEx4CE42xK8VAvwI8I cIk0rVWrJVCq3wAqx4xG67k08I80eVW5JVWrJwAqx4xG6c804VAFz4xC04v7Mc02F40Ew4 AK048IF2xKxVWUJVW8JwAqx4xG6xAIxVCFxsxG0wAv7VC0I7IYx2IY67AKxVWUJVWUGwAv 7VC2z280aVAFwI0_Jr0_Gr1lF7xvr2IY64vIr41l7480Y4vEI4kI2Ix0rVAqx4xJMxk0xI A0c2IEe2xFo4CEbIxvr21l42xK82IYc2Ij64vIr41lx4CE17CEb7AF67AKxVWUAVWUtwCI c40Y0x0EwIxGrbIYCTnIWIevJa73UjIFyTuYvjxU4tkuDUUUU
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQEKEko7lQ9FBwA7sK
Cc: "'mboned@ietf.org'" <mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 15 May 2012 01:47:07 -0000

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

Hi authors,

Some questions about the "possible solutions" proposed,

3.1, as stated by itself, probably not reasonable from implementation 
standpoint.

For 3.2 and the first approach in 3.3, I guess they're ALGs, and IMHO, 
the discussions in Section 4.1 of the 
http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00, are 
sufficient.

About the second approach in 3.3, not sure I fully understand it yet, 
but so far I see it also a kind of ALG.


Cheers,
Jacni

On 5/11/2012 Friday 1:49 AM, Tina TSOU wrote:
>
> Dear chairs,
>
> Would you ask the WG for adoption of 
> draft-tsou-mboned-multrans-addr-acquisition-01 as WG document?
>
> Thank you and have a good day.
>
> Tina and co-authors
>
> *From:*Tina TSOU
> *Sent:* Wednesday, May 02, 2012 11:58 AM
> *To:* mboned@ietf.org
> *Subject:* draft-tsou-mboned-multrans-addr-acquisition-01
>
> Now that the multicast transition framework document is officially 
> accepted, is the Working Group prepared also to take on the topic of 
> address acquisition, which is one of the tasks it identifies?
>
> If so, would draft-tsou-mboned-multrans-addr-acquisition-01 be 
> acceptable as a starting point?
>
> Tina
>
>
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

--------------020609080100080207020505
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">
    <font face="Calibri">Hi authors,<br>
      <br>
      Some questions about the "possible solutions" proposed,<br>
      <br>
      3.1, as stated by itself, probably not reasonable from
      implementation standpoint.<br>
      <br>
      For 3.2 and the first approach in 3.3, I guess they're ALGs, and
      IMHO, the discussions in Section 4.1 of the
      <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00">http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00</a>, are
      sufficient.<br>
      <br>
      About the second approach in 3.3, not sure I fully understand it
      yet, but so far I see it also a kind of ALG.<br>
      <br>
      <br>
      Cheers,<br>
      Jacni<br>
    </font><br>
    On 5/11/2012 Friday 1:49 AM, Tina TSOU wrote:
    <blockquote
cite="mid:C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="color:#1F497D">Dear chairs,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Would you ask
            the WG for adoption of
            draft-tsou-mboned-multrans-addr-acquisition-01 as WG
            document?<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Thank you and
            have a good day.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div>
          <p class="MsoNormal"><span style="color:#1F497D">Tina and
              co-authors<o:p></o:p></span></p>
        </div>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0in
          0in 0in 4.0pt">
          <div>
            <div style="border:none;border-top:solid #B5C4DF
              1.0pt;padding:3.0pt 0in 0in 0in">
              <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                  Tina TSOU
                  <br>
                  <b>Sent:</b> Wednesday, May 02, 2012 11:58 AM<br>
                  <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:mboned@ietf.org">mboned@ietf.org</a><br>
                  <b>Subject:</b>
                  draft-tsou-mboned-multrans-addr-acquisition-01<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          <p class="MsoPlainText">Now that the multicast transition
            framework document is officially accepted, is the Working
            Group prepared also to take on the topic of address
            acquisition, which is one of the tasks it identifies?<o:p></o:p></p>
          <p class="MsoNormal">If so, would
            draft-tsou-mboned-multrans-addr-acquisition-01 be acceptable
            as a starting point?<o:p></o:p></p>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          <p class="MsoNormal">Tina<o:p></o:p></p>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        </div>
      </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>
  </body>
</html>

--------------020609080100080207020505--


From cathy.zhou@huawei.com  Mon May 14 23:35:56 2012
Return-Path: <cathy.zhou@huawei.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 DA16511E8089 for <mboned@ietfa.amsl.com>; Mon, 14 May 2012 23:35:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599]
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 2n8-cFJbkWPF for <mboned@ietfa.amsl.com>; Mon, 14 May 2012 23:35:56 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 9C39211E8074 for <mboned@ietf.org>; Mon, 14 May 2012 23:35:48 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AGE79445; Tue, 15 May 2012 02:35:48 -0400 (EDT)
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 14 May 2012 23:32:18 -0700
Received: from SZXEML439-HUB.china.huawei.com (10.72.61.74) by dfweml405-hub.china.huawei.com (10.193.5.102) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 14 May 2012 23:32:17 -0700
Received: from SZXEML527-MBS.china.huawei.com ([169.254.6.180]) by szxeml439-hub.china.huawei.com ([10.72.61.74]) with mapi id 14.01.0323.003; Tue, 15 May 2012 14:32:11 +0800
From: "Zhouqian (Cathy)" <cathy.zhou@huawei.com>
To: Leonard Giuliano <lenny@juniper.net>, MBONED WG <mboned@ietf.org>
Thread-Topic: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
Thread-Index: Ac0olW4tpAJfzZWwTw2lKRKI4vlTgAGPwEowAL4DzoAAJeBUEA==
Date: Tue, 15 May 2012 06:32:10 +0000
Message-ID: <A6A061BEE5DDC94A9692D9D81AF776DF28DF1121@szxeml527-mbs.china.huawei.com>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com> <20120514132102.U91557@eng-mail01.juniper.net>
In-Reply-To: <20120514132102.U91557@eng-mail01.juniper.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.39.85]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 15 May 2012 06:35:57 -0000

I support adopting this document as a WG document.

Best Regards,
Cathy

-----Original Message-----
From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf Of=
 Leonard Giuliano
Sent: Tuesday, May 15, 2012 4:24 AM
To: MBONED WG
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01


We would like to poll the WG to decide if=20
draft-tsou-mboned-multrans-addr-acquisition-01 should be adopted as an=20
MBONED document.  Please respnd by May 29 if you thing this doc should or=20
should not be adopted by MBONED.


-MBONED Chairs


On Thu, 10 May 2012, Tina TSOU wrote:

-) Dear chairs,
-) Would you ask the WG for adoption of draft-tsou-mboned-multrans-addr-acq=
uisition-01 as WG document?
-)=20
-) Thank you and have a good day.
-)=20
-) Tina and co-authors
-)=20
-) From: Tina TSOU
-) Sent: Wednesday, May 02, 2012 11:58 AM
-) To: mboned@ietf.org
-) Subject: draft-tsou-mboned-multrans-addr-acquisition-01
-)=20
-)=20
-) Now that the multicast transition framework document is officially accep=
ted, is the Working Group prepared also to take on the topic of address acq=
uisition, which is one of the tasks it identifies?
-) If so, would draft-tsou-mboned-multrans-addr-acquisition-01 be acceptabl=
e as a starting point?
-)=20
-) Tina
-)=20
-)=20
_______________________________________________
MBONED mailing list
MBONED@ietf.org
https://www.ietf.org/mailman/listinfo/mboned

From mohamed.boucadair@orange.com  Tue May 15 04:30: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 C0DD821F86B7 for <mboned@ietfa.amsl.com>; Tue, 15 May 2012 04:30:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level: 
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[AWL=0.144,  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 GDZKGJ4as+Tr for <mboned@ietfa.amsl.com>; Tue, 15 May 2012 04:30: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 13E8E21F86B4 for <mboned@ietf.org>; Tue, 15 May 2012 04:30:29 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id D1DA918C566; Tue, 15 May 2012 13:30:28 +0200 (CEST)
Received: from PUEXCH11.nanterre.francetelecom.fr (unknown [10.101.44.27]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id B88C235C060; Tue, 15 May 2012 13:30:28 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH11.nanterre.francetelecom.fr ([10.101.44.27]) with mapi; Tue, 15 May 2012 13:30:28 +0200
From: <mohamed.boucadair@orange.com>
To: Leonard Giuliano <lenny@juniper.net>, MBONED WG <mboned@ietf.org>
Date: Tue, 15 May 2012 13:30:27 +0200
Thread-Topic: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
Thread-Index: Ac0yD6FGnv8c7JUAT8eBA73CPOStvAAfi/EQ
Message-ID: <94C682931C08B048B7A8645303FDC9F36E2A52D2C0@PUEXCB1B.nanterre.francetelecom.fr>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com> <20120514132102.U91557@eng-mail01.juniper.net>
In-Reply-To: <20120514132102.U91557@eng-mail01.juniper.net>
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.5.15.103315
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 15 May 2012 11:30:30 -0000

Dear all,

I do personally see a value to publish this document as a WG it; mainly the=
 discussion about potential extension to SDP to convey both IPv4 and IPv6 a=
ddresses.

I support the adoption of this document.

Cheers,
Med

>-----Message d'origine-----
>De : mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org]=20
>De la part de Leonard Giuliano
>Envoy=E9 : lundi 14 mai 2012 22:24
>=C0 : MBONED WG
>Objet : Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
>
>
>We would like to poll the WG to decide if=20
>draft-tsou-mboned-multrans-addr-acquisition-01 should be adopted as an=20
>MBONED document.  Please respnd by May 29 if you thing this=20
>doc should or=20
>should not be adopted by MBONED.
>
>
>-MBONED Chairs
>
>
>On Thu, 10 May 2012, Tina TSOU wrote:
>
>-) Dear chairs,
>-) Would you ask the WG for adoption of=20
>draft-tsou-mboned-multrans-addr-acquisition-01 as WG document?
>-)=20
>-) Thank you and have a good day.
>-)=20
>-) Tina and co-authors
>-)=20
>-) From: Tina TSOU
>-) Sent: Wednesday, May 02, 2012 11:58 AM
>-) To: mboned@ietf.org
>-) Subject: draft-tsou-mboned-multrans-addr-acquisition-01
>-)=20
>-)=20
>-) Now that the multicast transition framework document is=20
>officially accepted, is the Working Group prepared also to=20
>take on the topic of address acquisition, which is one of the=20
>tasks it identifies?
>-) If so, would draft-tsou-mboned-multrans-addr-acquisition-01=20
>be acceptable as a starting point?
>-)=20
>-) Tina
>-)=20
>-)=20
>_______________________________________________
>MBONED mailing list
>MBONED@ietf.org
>https://www.ietf.org/mailman/listinfo/mboned
>=

From sarikaya2012@gmail.com  Tue May 15 11:45:08 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 5F62321F887E; Tue, 15 May 2012 11:45:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.558
X-Spam-Level: 
X-Spam-Status: No, score=-3.558 tagged_above=-999 required=5 tests=[AWL=0.041,  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 h6IAteyUzRdX; Tue, 15 May 2012 11:45:07 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4DA3521F8734; Tue, 15 May 2012 11:45:07 -0700 (PDT)
Received: by obbeh20 with SMTP id eh20so11244212obb.31 for <multiple recipients>; Tue, 15 May 2012 11:45:06 -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:content-transfer-encoding; bh=XzyuWIbKzRdcW25gSqJs6P3rwjIUrfzCTWw3NUc5mPg=; b=UUv3ezuR6RpNgjU28EcVjH+3l4RrwBzPyoDTp/a0Os6WJOYYCew4ntYuJ6ALainhMS OBs6KPwFFWQG0aG27k3qaiteIL8TmueSBlKd19ganCiTMDQk6Q76JajapG7DUyCetNvW uFrxIPVQP9PhhrHIWSdVd73ql+xj1ytw4LA1dYreKnGuFezT/AGRUwalac4BUHXw+ZyF TJklDy4ysvV3lJGqJ5T5I2SF/FUqJzIyjhlL/00iFRVAlcgoCRawc//TYXMp2BELdo62 ih3l4m3BxwWKh+xkYE4t1vXIrahbaIGazGEvdxZPxV0+yWeaJpwiy24c+8h12pk1TpHE QcVg==
MIME-Version: 1.0
Received: by 10.182.235.16 with SMTP id ui16mr4371834obc.61.1337107506627; Tue, 15 May 2012 11:45:06 -0700 (PDT)
Received: by 10.60.164.103 with HTTP; Tue, 15 May 2012 11:45:06 -0700 (PDT)
In-Reply-To: <4FAC02D9.1050301@innovationslab.net>
References: <CBD0A398.20BF2%yiu_lee@cable.comcast.com> <4FAC02D9.1050301@innovationslab.net>
Date: Tue, 15 May 2012 13:45:06 -0500
Message-ID: <CAC8QAcceKvsdL-dDKOTQ1XmxZp3G1Y9tNr_7ScDWCvE1xp+3PA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Brian Haberman <brian@innovationslab.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "6man@ietf.org" <6man@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>, The IESG <iesg@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 15 May 2012 18:45:08 -0000

Hi Brian,

I think that there is a lot of confusion on the mails related to this
tread and some others regarding IPv4 IPv6 multicast work.

The confusion is stemming from the fact that multicast communication
is being abstracted from unicast communication.

I can not imagine any host being involved only in multicast
communication. In fact most of the communication will be in unicast.

For unicast communication, IETF has defined several transition
protocols, mostly in Softwire WG (ds-lite, 6rd, 4rd, etc.).

The right way to look at IPv4 IPv6 multicast is to look at these
unicast transition protocols and then define multicast protocols for
each.

In fact that is what we currently have. For each unicast transition
protocol we have a multicast transition protocol proposed/defined.


There is probably a single other component that is needed is the
address translation component. For this we have
draft-ietf-mboned-64-multicast-address-format.

However, there has been many objections to
draft-ietf-mboned-64-multicast-address-format because it is trying to
extend IP addressing architecture.

I do agree to those who say that we do not need to extend the
architecture and hope that a simpler solution can be found.

Please let's not get confused more and concentrate on finding the
right solution.

Regards,

Behcet

On Thu, May 10, 2012 at 1:03 PM, Brian Haberman
<brian@innovationslab.net> wrote:
> Hi Yiu,
> =A0 =A0 Let me ask a few questions...
>
>
> On 5/9/12 10:52 PM, Lee, Yiu wrote:
>>
>> Hi Carsten,
>>
>> Thanks very much for reviewing the document. I just want to add a point =
to
>> your question about how applications decide when to use this multicast
>> address format. In fact, they don't. Imagine a use case where a legacy
>> IPv4 IP-TV receiver (an app) wants to join a channel which is broadcaste=
d
>> in IPv6. The app will continue to send the igmp-join (say 224.1.2.3).
>
>
> How does the IPv4 IP-TV know to join 224.1.2.3?
>
> How is 224.1.2.3 advertised to the IPv4 IP-TV clients if the content is
> generated by an IPv6 source? =A0Does the source need to be configured to =
use
> one of these IPv4-in-IPv6 multicast addresses?
>
>
>> There will be a function in the network which is statically configured
>> that when it receives a igmp-join, it would covert to a corresponding
>> mld-join. The IPv6 address in the join message will follow what is
>> described in this draft. This Adaptive Function is transparent to the
>> application and managed by the network.
>
>
> Are you limiting this approach to only mapping at the IGMP/MLD protocols?
>
> How does your Adaptive Function know which IPv6 multicast prefix to use w=
hen
> mapping the IPv4 multicast address in the IGMP Report message to MLD?
>
> Regards,
> Brian
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From Tina.Tsou.Zouting@huawei.com  Tue May 15 13:26:21 2012
Return-Path: <Tina.Tsou.Zouting@huawei.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 35E3611E8073 for <mboned@ietfa.amsl.com>; Tue, 15 May 2012 13:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.482
X-Spam-Level: 
X-Spam-Status: No, score=-2.482 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, HTML_MESSAGE=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 14ATVtaMfEY7 for <mboned@ietfa.amsl.com>; Tue, 15 May 2012 13:26:20 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 7547221F884F for <mboned@ietf.org>; Tue, 15 May 2012 13:26:20 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AGF39072; Tue, 15 May 2012 16:26:20 -0400 (EDT)
Received: from DFWEML403-HUB.china.huawei.com (10.193.5.151) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 15 May 2012 13:24:54 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.80]) by dfweml403-hub.china.huawei.com ([10.193.5.151]) with mapi id 14.01.0323.003; Tue, 15 May 2012 13:24:37 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Jacni Qin <jacni@jacni.com>
Thread-Topic: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
Thread-Index: Ac0olW4tpAJfzZWwTw2lKRKI4vlTgAGPwEowAOi2jQAAGFECkA==
Date: Tue, 15 May 2012 20:24:36 +0000
Message-ID: <C0E0A32284495243BDE0AC8A066631A80D3858EC@dfweml513-mbx.china.huawei.com>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com> <4FB1B592.1090706@jacni.com>
In-Reply-To: <4FB1B592.1090706@jacni.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.193.34.151]
Content-Type: multipart/alternative; boundary="_000_C0E0A32284495243BDE0AC8A066631A80D3858ECdfweml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "'mboned@ietf.org'" <mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 15 May 2012 20:26:21 -0000

--_000_C0E0A32284495243BDE0AC8A066631A80D3858ECdfweml513mbxchi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable



Tina

From: Jacni Qin [mailto:jacni@jacni.com]
Sent: Monday, May 14, 2012 6:47 PM
To: Tina TSOU
Cc: Leonard Giuliano; Greg Shepherd; 'mboned@ietf.org'
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01

Hi authors,

Some questions about the "possible solutions" proposed,

3.1, as stated by itself, probably not reasonable from implementation stand=
point.

For 3.2 and the first approach in 3.3, I guess they're ALGs, and IMHO, the =
discussions in Section 4.1 of the http://tools.ietf.org/html/draft-ietf-mbo=
ned-v4v6-mcast-ps-00, are sufficient.

[Tina] R u suggesting that the Problem Statement is going too far into solu=
tion descriptions and should be cut back?

About the second approach in 3.3, not sure I fully understand it yet, but s=
o far I see it also a kind of ALG.



Cheers,
Jacni

On 5/11/2012 Friday 1:49 AM, Tina TSOU wrote:
Dear chairs,
Would you ask the WG for adoption of draft-tsou-mboned-multrans-addr-acquis=
ition-01 as WG document?

Thank you and have a good day.

Tina and co-authors

From: Tina TSOU
Sent: Wednesday, May 02, 2012 11:58 AM
To: mboned@ietf.org<mailto:mboned@ietf.org>
Subject: draft-tsou-mboned-multrans-addr-acquisition-01


Now that the multicast transition framework document is officially accepted=
, is the Working Group prepared also to take on the topic of address acquis=
ition, which is one of the tasks it identifies?
If so, would draft-tsou-mboned-multrans-addr-acquisition-01 be acceptable a=
s a starting point?

Tina





_______________________________________________

MBONED mailing list

MBONED@ietf.org<mailto:MBONED@ietf.org>

https://www.ietf.org/mailman/listinfo/mboned

--_000_C0E0A32284495243BDE0AC8A066631A80D3858ECdfweml513mbxchi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Tina<o:p></o:p></span>=
</p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext"> Jacni Qin [mailto:jacni@jacni.com]
<br>
<b>Sent:</b> Monday, May 14, 2012 6:47 PM<br>
<b>To:</b> Tina TSOU<br>
<b>Cc:</b> Leonard Giuliano; Greg Shepherd; 'mboned@ietf.org'<br>
<b>Subject:</b> Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01=
<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi authors,<br>
<br>
Some questions about the &quot;possible solutions&quot; proposed,<br>
<br>
3.1, as stated by itself, probably not reasonable from implementation stand=
point.<br>
<br>
For 3.2 and the first approach in 3.3, I guess they're ALGs, and IMHO, the =
discussions in Section 4.1 of the
<a href=3D"http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00">h=
ttp://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00</a>, are suffi=
cient.<span style=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">[Tina] R u suggesting =
that the Problem Statement is going too far into solution descriptions and =
should be cut back?</span><br>
<br>
About the second approach in 3.3, not sure I fully understand it yet, but s=
o far I see it also a kind of ALG.<span style=3D"color:#1F497D"><o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><br>
<br>
<br>
Cheers,<br>
Jacni<br>
<br>
On 5/11/2012 Friday 1:49 AM, Tina TSOU wrote: <o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Dear chairs,</span><o:=
p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Would you ask the WG f=
or adoption of draft-tsou-mboned-multrans-addr-acquisition-01 as WG documen=
t?</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thank you and have a g=
ood day.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Tina and co-authors</s=
pan><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Tina TSO=
U
<br>
<b>Sent:</b> Wednesday, May 02, 2012 11:58 AM<br>
<b>To:</b> <a href=3D"mailto:mboned@ietf.org">mboned@ietf.org</a><br>
<b>Subject:</b> draft-tsou-mboned-multrans-addr-acquisition-01</span><o:p><=
/o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">Now that the multicast transition framework docum=
ent is officially accepted, is the Working Group prepared also to take on t=
he topic of address acquisition, which is one of the tasks it identifies?<o=
:p></o:p></p>
<p class=3D"MsoNormal">If so, would draft-tsou-mboned-multrans-addr-acquisi=
tion-01 be acceptable as a starting point?<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Tina<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>MBONED mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:MBONED@ietf.org">MBONED@ietf.org</a><o:p></o:p></pre=
>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/mboned">https://www.i=
etf.org/mailman/listinfo/mboned</a><o:p></o:p></pre>
</div>
</div>
</body>
</html>

--_000_C0E0A32284495243BDE0AC8A066631A80D3858ECdfweml513mbxchi_--

From albert.e.manfredi@boeing.com  Tue May 15 15:07:49 2012
Return-Path: <albert.e.manfredi@boeing.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 2671621F8622 for <mboned@ietfa.amsl.com>; Tue, 15 May 2012 15:07:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.882
X-Spam-Level: 
X-Spam-Status: No, score=-4.882 tagged_above=-999 required=5 tests=[AWL=-2.284, BAYES_00=-2.599, HTML_MESSAGE=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 OKs+nIO2KDOG for <mboned@ietfa.amsl.com>; Tue, 15 May 2012 15:07:46 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id CA23421F861E for <mboned@ietf.org>; Tue, 15 May 2012 15:07:46 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id q4FM7kHT011295 for <mboned@ietf.org>; Tue, 15 May 2012 15:07:46 -0700
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.16.37]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id q4FM7jxb011280 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 15 May 2012 15:07:45 -0700
Received: from blv-av-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id q4FM7ijw009329; Tue, 15 May 2012 15:07:44 -0700
Received: from XCH-MWHT-05.mw.nos.boeing.com (xch-mwht-05.mw.nos.boeing.com [134.57.119.160]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q4FM7h5P009289 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Tue, 15 May 2012 15:07:44 -0700
Received: from XCH-MW-08V.mw.nos.boeing.com ([134.57.119.191]) by XCH-MWHT-05.mw.nos.boeing.com ([134.57.119.160]) with mapi; Tue, 15 May 2012 17:07:43 -0500
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Date: Tue, 15 May 2012 17:07:41 -0500
Thread-Topic: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
Thread-Index: Ac0yPKmzPC059CtPTei9W6XIQTjHvwApXaqA
Message-ID: <B0147C3DD45E42478038FC347CCB65FE02BB90F50B@XCH-MW-08V.mw.nos.boeing.com>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com> <4FB1B592.1090706@jacni.com>
In-Reply-To: <4FB1B592.1090706@jacni.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_B0147C3DD45E42478038FC347CCB65FE02BB90F50BXCHMW08Vmwnos_"
MIME-Version: 1.0
X-TM-AS-MML: No
Cc: "'mboned@ietf.org'" <mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 15 May 2012 22:07:49 -0000

--_000_B0147C3DD45E42478038FC347CCB65FE02BB90F50BXCHMW08Vmwnos_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Tina et al,

I also support this effort. A couple of comments:

My reaction to the Reactive Strategy in 3.1 was that it's too hard. Instead=
 of making the IPv4 receiver kludge up IPv6 addresses, presumably kludge up=
 MLD(?), and then convert IPv6 multicasts, why not just install an IPv6 sta=
ck in that receiver? (And yet, the counter to this is that Microsoft Office=
 2003 is capable of ingesting Office 2007 files quite well, and maybe even =
Office 2010 files, and all done in the "receiver." Still, Office suites are=
 expensive for users, whereas IP stacks are not.)

The Dynamic Modification in 3.2, by the network, seems to be a more realist=
ic option.

The Administrative Preparation in 3.3 seems to be an elaboration of 3.2. It=
 merely adds a description of mechanisms that may be used to obtain info on=
 the receiver, where 3.2 only said:

   It requires that an element in that network must
   intercept program guide information destined to the receiver, locate
   the access information, and map IP addresses to an alternate version
   as necessary to suit the receiver.

Isn't 3.3 describing HOW the network knows to "suit the receiver"?

Another option would be for the network to transfer both multicasts, and si=
mply respond according to whether the receiver used IGMP or MLD to join the=
 multicast. And the receiver would know the appropriate IPv4 or IPv6 multic=
ast group (and potentially source IP) using OOB means, like the EPG itself,=
 or the EPG plus an associated SIP session, or EPG plus SDP. (Wasn't there =
a discussion some time ago about "why use SDP anymore?") Assuming bandwidth=
 isn't in very short supply, my own approach would be either to get both ve=
rsions from the source, or to create the other version at the initial ingre=
ss point to my network.

Bert


From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf Of=
 Jacni Qin
Sent: Monday, May 14, 2012 9:47 PM
To: Tina TSOU
Cc: 'mboned@ietf.org'
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01

Hi authors,

Some questions about the "possible solutions" proposed,

3.1, as stated by itself, probably not reasonable from implementation stand=
point.

For 3.2 and the first approach in 3.3, I guess they're ALGs, and IMHO, the =
discussions in Section 4.1 of the http://tools.ietf.org/html/draft-ietf-mbo=
ned-v4v6-mcast-ps-00, are sufficient.

About the second approach in 3.3, not sure I fully understand it yet, but s=
o far I see it also a kind of ALG.


Cheers,
Jacni

On 5/11/2012 Friday 1:49 AM, Tina TSOU wrote:
Dear chairs,
Would you ask the WG for adoption of draft-tsou-mboned-multrans-addr-acquis=
ition-01 as WG document?

Thank you and have a good day.

Tina and co-authors

From: Tina TSOU
Sent: Wednesday, May 02, 2012 11:58 AM
To: mboned@ietf.org<mailto:mboned@ietf.org>
Subject: draft-tsou-mboned-multrans-addr-acquisition-01


Now that the multicast transition framework document is officially accepted=
, is the Working Group prepared also to take on the topic of address acquis=
ition, which is one of the tasks it identifies?
If so, would draft-tsou-mboned-multrans-addr-acquisition-01 be acceptable a=
s a starting point?

Tina





_______________________________________________

MBONED mailing list

MBONED@ietf.org<mailto:MBONED@ietf.org>

https://www.ietf.org/mailman/listinfo/mboned

--_000_B0147C3DD45E42478038FC347CCB65FE02BB90F50BXCHMW08Vmwnos_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Times New Roman","serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite lang=3DEN-US=
 link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>=
<span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color=
:blue'>Tina et al,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:12.0pt;font-family:"Times New Roman","serif";color:blue'><o:p>&n=
bsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;f=
ont-family:"Times New Roman","serif";color:blue'>I also support this effort=
. A couple of comments:<o:p></o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:blue'><o=
:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.=
0pt;font-family:"Times New Roman","serif";color:blue'>My reaction to the Re=
active Strategy in 3.1 was that it&#8217;s too hard. Instead of making the =
IPv4 receiver kludge up IPv6 addresses, presumably kludge up MLD(?), and th=
en convert IPv6 multicasts, why not just install an IPv6 stack in that rece=
iver? (And yet, the counter to this is that Microsoft Office 2003 is capabl=
e of ingesting Office 2007 files quite well, and maybe even Office 2010 fil=
es, and all done in the &#8220;receiver.&#8221; Still, Office suites are ex=
pensive for users, whereas IP stacks are not.)<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New Roman"=
,"serif";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:blue=
'>The Dynamic Modification in 3.2, by the network, seems to be a more reali=
stic option.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:12.0pt;font-family:"Times New Roman","serif";color:blue'><o:p>&nbsp;</=
o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-fa=
mily:"Times New Roman","serif";color:blue'>The Administrative Preparation i=
n 3.3 seems to be an elaboration of 3.2. It merely adds a description of me=
chanisms that may be used to obtain info on the receiver, where 3.2 only sa=
id:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0=
pt;font-family:"Times New Roman","serif";color:blue'><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoNormal style=3D'line-height:14.4pt'><span style=3D'font=
-size:10.0pt;font-family:"Courier New";color:windowtext'>&nbsp;&nbsp; It re=
quires that an element in that network must<o:p></o:p></span></p><p class=
=3DMsoNormal style=3D'line-height:14.4pt'><span style=3D'font-size:10.0pt;f=
ont-family:"Courier New";color:windowtext'>&nbsp;&nbsp; intercept program g=
uide information destined to the receiver, locate<o:p></o:p></span></p><p c=
lass=3DMsoNormal style=3D'line-height:14.4pt'><span style=3D'font-size:10.0=
pt;font-family:"Courier New";color:windowtext'>&nbsp;&nbsp; the access info=
rmation, and map IP addresses to an alternate version<o:p></o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier N=
ew";color:windowtext'>&nbsp;&nbsp; as necessary to suit the receiver.</span=
><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";colo=
r:blue'> <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:12.0pt;font-family:"Times New Roman","serif";color:blue'><o:p>&nbsp;</o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-famil=
y:"Times New Roman","serif";color:blue'>Isn&#8217;t 3.3 describing HOW the =
network knows to &#8220;suit the receiver&#8221;?<o:p></o:p></span></p><p c=
lass=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New Rom=
an","serif";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:b=
lue'>Another option would be for the network to transfer both multicasts, a=
nd simply respond according to whether the receiver used IGMP or MLD to joi=
n the multicast. And the receiver would know the appropriate IPv4 or IPv6 m=
ulticast group (and potentially source IP) using OOB means, like the EPG it=
self, or the EPG plus an associated SIP session, or EPG plus SDP. (Wasn&#82=
17;t there a discussion some time ago about &#8220;why use SDP anymore?&#82=
21;) Assuming bandwidth isn&#8217;t in very short supply, my own approach w=
ould be either to get both versions from the source, or to create the other=
 version at the initial ingress point to my network.<o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";colo=
r:blue'>Bert<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:12.0pt;font-family:"Times New Roman","serif";color:blue'><o:p>&nbsp;</=
o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-fa=
mily:"Times New Roman","serif";color:blue'><o:p>&nbsp;</o:p></span></p><div=
><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in=
 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-fami=
ly:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> mboned=
-bounces@ietf.org [mailto:mboned-bounces@ietf.org] <b>On Behalf Of </b>Jacn=
i Qin<br><b>Sent:</b> Monday, May 14, 2012 9:47 PM<br><b>To:</b> Tina TSOU<=
br><b>Cc:</b> 'mboned@ietf.org'<br><b>Subject:</b> Re: [MBONED] draft-tsou-=
mboned-multrans-addr-acquisition-01<o:p></o:p></span></p></div></div><p cla=
ss=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Hi authors,<br><br=
>Some questions about the &quot;possible solutions&quot; proposed,<br><br>3=
.1, as stated by itself, probably not reasonable from implementation standp=
oint.<br><br>For 3.2 and the first approach in 3.3, I guess they're ALGs, a=
nd IMHO, the discussions in Section 4.1 of the <a href=3D"http://tools.ietf=
.org/html/draft-ietf-mboned-v4v6-mcast-ps-00">http://tools.ietf.org/html/dr=
aft-ietf-mboned-v4v6-mcast-ps-00</a>, are sufficient.<br><br>About the seco=
nd approach in 3.3, not sure I fully understand it yet, but so far I see it=
 also a kind of ALG.<br><br><br>Cheers,<br>Jacni<br><br>On 5/11/2012 Friday=
 1:49 AM, Tina TSOU wrote: <o:p></o:p></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'>Dear chairs,</span><o:p></o:p></p><p class=3DMsoNormal><=
span style=3D'color:#1F497D'>Would you ask the WG for adoption of draft-tso=
u-mboned-multrans-addr-acquisition-01 as WG document?</span><o:p></o:p></p>=
<p class=3DMsoNormal><span style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p>=
</p><p class=3DMsoNormal><span style=3D'color:#1F497D'>Thank you and have a=
 good day.</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'color:#=
1F497D'>&nbsp;</span><o:p></o:p></p><div><p class=3DMsoNormal><span style=
=3D'color:#1F497D'>Tina and co-authors</span><o:p></o:p></p></div><p class=
=3DMsoNormal><span style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><div=
 style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0p=
t'><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.=
0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;fo=
nt-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:1=
0.0pt;font-family:"Tahoma","sans-serif"'> Tina TSOU <br><b>Sent:</b> Wednes=
day, May 02, 2012 11:58 AM<br><b>To:</b> <a href=3D"mailto:mboned@ietf.org"=
>mboned@ietf.org</a><br><b>Subject:</b> draft-tsou-mboned-multrans-addr-acq=
uisition-01</span><o:p></o:p></p></div></div><p class=3DMsoNormal>&nbsp;<o:=
p></o:p></p><p class=3DMsoPlainText>Now that the multicast transition frame=
work document is officially accepted, is the Working Group prepared also to=
 take on the topic of address acquisition, which is one of the tasks it ide=
ntifies?<o:p></o:p></p><p class=3DMsoNormal>If so, would draft-tsou-mboned-=
multrans-addr-acquisition-01 be acceptable as a starting point?<o:p></o:p><=
/p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>Tina<o:p>=
</o:p></p><p class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><p class=3DMsoNor=
mal><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'>=
<br><br><br><o:p></o:p></span></p><pre>____________________________________=
___________<o:p></o:p></pre><pre>MBONED mailing list<o:p></o:p></pre><pre><=
a href=3D"mailto:MBONED@ietf.org">MBONED@ietf.org</a><o:p></o:p></pre><pre>=
<a href=3D"https://www.ietf.org/mailman/listinfo/mboned">https://www.ietf.o=
rg/mailman/listinfo/mboned</a><o:p></o:p></pre></div></body></html>=

--_000_B0147C3DD45E42478038FC347CCB65FE02BB90F50BXCHMW08Vmwnos_--


From jacni@jacni.com  Tue May 15 17:44: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 BE84121F86A0 for <mboned@ietfa.amsl.com>; Tue, 15 May 2012 17:44:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.943
X-Spam-Level: 
X-Spam-Status: No, score=-1.943 tagged_above=-999 required=5 tests=[AWL=0.344,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=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 OJxTTYnVnFwr for <mboned@ietfa.amsl.com>; Tue, 15 May 2012 17:44:24 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 31CAA21F869E for <mboned@ietf.org>; Tue, 15 May 2012 17:44:23 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 68C5F3800E7 for <mboned@ietf.org>; Tue, 15 May 2012 20:44:22 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with ESMTP id DCF1C3400C4 for <mboned@ietf.org>; Wed, 16 May 2012 08:44:20 +0800 (CST)
Received: from [10.140.20.37] (unknown [64.104.125.217]) by app (Coremail) with SMTP id +AWowJDbj4lh+LJPyD_1AA--.30023S2; Wed, 16 May 2012 08:44:19 +0800 (CST)
Message-ID: <4FB2F85F.60805@jacni.com>
Date: Wed, 16 May 2012 08:44:15 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com> <4FB1B592.1090706@jacni.com> <C0E0A32284495243BDE0AC8A066631A80D3858EC@dfweml513-mbx.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80D3858EC@dfweml513-mbx.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------060105000204000204040206"
X-CM-TRANSID: +AWowJDbj4lh+LJPyD_1AA--.30023S2
X-Coremail-Antispam: 1UD129KBjvJXoW7ZrWfCFWrGry7tr18KrW5trb_yoW8ZF1fpa 17Way7Kr4kJr4xC348ZF4rGr1F9FyUtrWUGF98Kr1jvFW5WF18Kw1av3y5t34UGrn8Aa4D ZF1xu34DuF13Z37anT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUU2Cb7Iv0xC_Cr1lb4IE77IF4wAFc2x0x2IEx4CE42xK8VAvwI8I cIk0rVWrJVCq3wAqx4xG67k08I80eVW5JVWrJwAqx4xG6c804VAFz4xC04v7Mc02F40Ew4 AK048IF2xKxVWUJVW8JwAqx4xG6xAIxVCFxsxG0wAqx4xG6I80eVA0xI0YY7vIx2IE14AG zxvEb7x7McIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8JwACjcxG0x vEwIxGrwCjr7xvwVCIw2I0I7xG6c02F41lc7I2V7IY0VAS07AlzVAYIcxG8wCF04k20xvY 0x0EwIxGrwC2zVAF1VAY17CE14v26r126r1DMIIYrxkI7VAKI48JYxBIdaVFxhVjvjDU0x ZFpf9x07jzyIUUUUUU=
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQEKEko7lQ9FBwBIs5
Cc: "'mboned@ietf.org'" <mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 16 May 2012 00:44:24 -0000

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

Re-,

On 5/16/2012 Wednesday 4:24 AM, Tina TSOU wrote:
>
> Tina
>
> *From:*Jacni Qin [mailto:jacni@jacni.com]
> *Sent:* Monday, May 14, 2012 6:47 PM
> *To:* Tina TSOU
> *Cc:* Leonard Giuliano; Greg Shepherd; 'mboned@ietf.org'
> *Subject:* Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
>
> Hi authors,
>
> Some questions about the "possible solutions" proposed,
>
> 3.1, as stated by itself, probably not reasonable from implementation 
> standpoint.
>
> For 3.2 and the first approach in 3.3, I guess they're ALGs,
>
Sorry, some words missed, "... they're ALGs and manual configuration, ..."

> and IMHO, the discussions in Section 4.1 of the 
> http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00, are 
> sufficient.
>
> [Tina] R u suggesting that the Problem Statement is going too far into 
> solution descriptions and should be cut back?
>
No, I don't think most of these are solutions, but just sort of analysis 
of deployment, to describe issues/problems maybe encountered, which have 
been discussed sufficiently in the Problem Statement.


Cheers,
Jacni
>
> About the second approach in 3.3, not sure I fully understand it yet, 
> but so far I see it also a kind of ALG.
>
>
>
>
> Cheers,
> Jacni
>
> On 5/11/2012 Friday 1:49 AM, Tina TSOU wrote:
>
> Dear chairs,
>
> Would you ask the WG for adoption of 
> draft-tsou-mboned-multrans-addr-acquisition-01 as WG document?
>
> Thank you and have a good day.
>
> Tina and co-authors
>
> *From:*Tina TSOU
> *Sent:* Wednesday, May 02, 2012 11:58 AM
> *To:* mboned@ietf.org <mailto:mboned@ietf.org>
> *Subject:* draft-tsou-mboned-multrans-addr-acquisition-01
>
> Now that the multicast transition framework document is officially 
> accepted, is the Working Group prepared also to take on the topic of 
> address acquisition, which is one of the tasks it identifies?
>
> If so, would draft-tsou-mboned-multrans-addr-acquisition-01 be 
> acceptable as a starting point?
>
> Tina
>
>
>
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org  <mailto:MBONED@ietf.org>
> https://www.ietf.org/mailman/listinfo/mboned

--------------060105000204000204040206
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">
    <font face="Calibri">Re-,</font><br>
    <br>
    On 5/16/2012 Wednesday 4:24 AM, Tina TSOU wrote:
    <blockquote
cite="mid:C0E0A32284495243BDE0AC8A066631A80D3858EC@dfweml513-mbx.china.huawei.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div>
          <p class="MsoNormal"><span style="color:#1F497D">Tina<o:p></o:p></span></p>
        </div>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <div style="border-width: medium medium medium 1.5pt;
          border-style: none none none solid; border-color:
          -moz-use-text-color -moz-use-text-color -moz-use-text-color
          blue; -moz-border-top-colors: none; -moz-border-right-colors:
          none; -moz-border-bottom-colors: none;
          -moz-border-left-colors: none; -moz-border-image: none;
          padding: 0in 0in 0in 4pt;">
          <div>
            <div style="border:none;border-top:solid #B5C4DF
              1.0pt;padding:3.0pt 0in 0in 0in">
              <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">
                  Jacni Qin [<a class="moz-txt-link-freetext" href="mailto:jacni@jacni.com">mailto:jacni@jacni.com</a>]
                  <br>
                  <b>Sent:</b> Monday, May 14, 2012 6:47 PM<br>
                  <b>To:</b> Tina TSOU<br>
                  <b>Cc:</b> Leonard Giuliano; Greg Shepherd;
                  '<a class="moz-txt-link-abbreviated" href="mailto:mboned@ietf.org">mboned@ietf.org</a>'<br>
                  <b>Subject:</b> Re: [MBONED]
                  draft-tsou-mboned-multrans-addr-acquisition-01<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
          <p class="MsoNormal">Hi authors,<br>
            <br>
            Some questions about the "possible solutions" proposed,<br>
            <br>
            3.1, as stated by itself, probably not reasonable from
            implementation standpoint.<br>
            <br>
            For 3.2 and the first approach in 3.3, I guess they're ALGs,
          </p>
        </div>
      </div>
    </blockquote>
    Sorry, some words missed, "... they're ALGs and manual
    configuration, ..."<br>
    <br>
    <blockquote
cite="mid:C0E0A32284495243BDE0AC8A066631A80D3858EC@dfweml513-mbx.china.huawei.com"
      type="cite">
      <div class="WordSection1">
        <div style="border-width: medium medium medium 1.5pt;
          border-style: none none none solid; border-color:
          -moz-use-text-color -moz-use-text-color -moz-use-text-color
          blue; -moz-border-top-colors: none; -moz-border-right-colors:
          none; -moz-border-bottom-colors: none;
          -moz-border-left-colors: none; -moz-border-image: none;
          padding: 0in 0in 0in 4pt;">
          <p class="MsoNormal">and IMHO, the discussions in Section 4.1
            of the
            <a moz-do-not-send="true"
              href="http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00">http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00</a>,
            are sufficient.<span style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal"><span style="color:#1F497D">[Tina] R u
              suggesting that the Problem Statement is going too far
              into solution descriptions and should be cut back?</span><br>
            <br>
          </p>
        </div>
      </div>
    </blockquote>
    No, I don't think most of these are solutions, but just sort of
    analysis of deployment, to describe issues/problems maybe
    encountered, which have been discussed sufficiently in the Problem
    Statement.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <blockquote
cite="mid:C0E0A32284495243BDE0AC8A066631A80D3858EC@dfweml513-mbx.china.huawei.com"
      type="cite">
      <div class="WordSection1">
        <div style="border:none;border-left:solid blue 1.5pt;padding:0in
          0in 0in 4.0pt">
          <p class="MsoNormal">
            About the second approach in 3.3, not sure I fully
            understand it yet, but so far I see it also a kind of ALG.<span
              style="color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><br>
            <br>
            <br>
            Cheers,<br>
            Jacni<br>
            <br>
            On 5/11/2012 Friday 1:49 AM, Tina TSOU wrote: <o:p></o:p></p>
          <p class="MsoNormal"><span style="color:#1F497D">Dear chairs,</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="color:#1F497D">Would you ask
              the WG for adoption of
              draft-tsou-mboned-multrans-addr-acquisition-01 as WG
              document?</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="color:#1F497D">&nbsp;</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="color:#1F497D">Thank you and
              have a good day.</span><o:p></o:p></p>
          <p class="MsoNormal"><span style="color:#1F497D">&nbsp;</span><o:p></o:p></p>
          <div>
            <p class="MsoNormal"><span style="color:#1F497D">Tina and
                co-authors</span><o:p></o:p></p>
          </div>
          <p class="MsoNormal"><span style="color:#1F497D">&nbsp;</span><o:p></o:p></p>
          <div style="border:none;border-left:solid blue
            1.5pt;padding:0in 0in 0in 4.0pt">
            <div>
              <div style="border:none;border-top:solid #B5C4DF
                1.0pt;padding:3.0pt 0in 0in 0in">
                <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
                    Tina TSOU
                    <br>
                    <b>Sent:</b> Wednesday, May 02, 2012 11:58 AM<br>
                    <b>To:</b> <a moz-do-not-send="true"
                      href="mailto:mboned@ietf.org">mboned@ietf.org</a><br>
                    <b>Subject:</b>
                    draft-tsou-mboned-multrans-addr-acquisition-01</span><o:p></o:p></p>
              </div>
            </div>
            <p class="MsoNormal">&nbsp;<o:p></o:p></p>
            <p class="MsoPlainText">Now that the multicast transition
              framework document is officially accepted, is the Working
              Group prepared also to take on the topic of address
              acquisition, which is one of the tasks it identifies?<o:p></o:p></p>
            <p class="MsoNormal">If so, would
              draft-tsou-mboned-multrans-addr-acquisition-01 be
              acceptable as a starting point?<o:p></o:p></p>
            <p class="MsoNormal">&nbsp;<o:p></o:p></p>
            <p class="MsoNormal">Tina<o:p></o:p></p>
            <p class="MsoNormal">&nbsp;<o:p></o:p></p>
          </div>
          <p class="MsoNormal"><span
              style="font-size:12.0pt;font-family:&quot;Times New
              Roman&quot;,&quot;serif&quot;"><br>
              <br>
              <br>
              <o:p></o:p></span></p>
          <pre>_______________________________________________<o:p></o:p></pre>
          <pre>MBONED mailing list<o:p></o:p></pre>
          <pre><a moz-do-not-send="true" href="mailto:MBONED@ietf.org">MBONED@ietf.org</a><o:p></o:p></pre>
          <pre><a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/mboned">https://www.ietf.org/mailman/listinfo/mboned</a><o:p></o:p></pre>
        </div>
      </div>
    </blockquote>
  </body>
</html>

--------------060105000204000204040206--


From jacni@jacni.com  Tue May 15 18:20:52 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 0221721F86A5; Tue, 15 May 2012 18:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.986
X-Spam-Level: 
X-Spam-Status: No, score=-1.986 tagged_above=-999 required=5 tests=[AWL=0.301,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=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 1JNWZiMxeHxX; Tue, 15 May 2012 18:20:51 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 2FD9F21F86A4; Tue, 15 May 2012 18:20:51 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 5EC803800E9; Tue, 15 May 2012 21:20:47 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with ESMTP id 05162340105; Wed, 16 May 2012 09:20:46 +0800 (CST)
Received: from [10.140.20.37] (unknown [64.104.125.217]) by app (Coremail) with SMTP id +AWowJDrH43sALNPt0_1AA--.2450S2; Wed, 16 May 2012 09:20:45 +0800 (CST)
Message-ID: <4FB300E9.60505@jacni.com>
Date: Wed, 16 May 2012 09:20:41 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
References: <CBD6EB81.20E9E%yiu_lee@cable.comcast.com>
In-Reply-To: <CBD6EB81.20E9E%yiu_lee@cable.comcast.com>
Content-Type: multipart/alternative; boundary="------------090903050302090805080501"
X-CM-TRANSID: +AWowJDrH43sALNPt0_1AA--.2450S2
X-Coremail-Antispam: 1UD129KBjvJXoWxWryrZF1UuryUKw1fGryUZFb_yoW5WFW8pa y8Ww4UGr4kGrn3Ca97Jw409rySyFn5G345Ary5G345u3y5Ca4SkryYk3y5ta4DGr90ya1j 9rWj9ryUZF1kA3DanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnL8YjsxI4VWkKwAYFVCjjxCrM7CY07I20VC2zVCF04k26cxKx2IYs7xG 6rWj6s0DMcIj6xIIjxv20xvE14v26r106r15McIj6I8E87Iv67AKxVWUJVW8JwACjcxG0x vEwIxGrwCjr7xvwVCIw2I0I7xG6c02F41lc7I2V7IY0VAS07AlzVAYIcxG8wCF04k20xvY 0x0EwIxGrwC2zVAF1VAY17CE14v26r126r1DMIIYrxkI7VAKI48JYxBIdaVFxhVjvjDU0x ZFpf9x07jr4SrUUUUU=
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQEKEko7lQ9FBwBLs6
Cc: "6man@ietf.org" <6man@ietf.org>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, "draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org" <draft-ietf-mboned-64-multicast-address-format.all@tools.ietf.org>, Stig Venaas <stig@cisco.com>, The IESG <iesg@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] APPSDIR review of draft-ietf-mboned-64-multicast-address-format-01
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, 16 May 2012 01:20:52 -0000

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

Re-,

On 5/15/2012 Tuesday 5:06 AM, Lee, Yiu wrote:
> Hi Stig,
>
> Right. I explain only one use case. Other may find the latter case is more
> attractive for their deployments. This address format should enable the
> dynamic use case as well.
Yes, imaging the coexistence of the native provisioning and the embedded 
address for some transition approach deployment, to perform that 
statelessly, a flag bit is efficient.


Cheers,
Jacni

> Yiu
>
> On 5/14/12 4:56 PM, "Stig Venaas"<stig@cisco.com>  wrote:
>
>> On 5/14/2012 1:50 PM, Lee, Yiu wrote:
>>> Hi Brian,
>>>
>>> Sorry for getting back late. I read Bert's answers to your questions.
>>> His
>>> answers are inline with my answers. Most information are statically
>>> configured. For example: Ch1 is statically configured to 224.1.2.3 via
>>> OOB
>>> mechanism. If the STB is IPv4 only, it will only use IPv4 mcast address.
>>> It won't use the address format defined in this draft. In my mind, the
>>> most common deployment will use the same IPv6 prefix which will be
>>> statically configured in the AF.
>> Right, so that was my main concern with the draft. Is static
>> configuration like this sufficient, or are there more generic cases
>> where one needs to know that it is translated from IPv4 without a
>> priori configuration. The flag bit (or a well-known prefix) is only
>> needed in the latter case. I know there were some scenarios where
>> someone found the latter to be advantageous though.
>>
>> Stig
>>
>>> Regards,
>>> Yiu
>>>
>>>
>>> On 5/10/12 2:03 PM, "Brian Haberman"<brian@innovationslab.net>   wrote:
>>>
>>>> Hi Yiu,
>>>>        Let me ask a few questions...
>>>>
>>>> On 5/9/12 10:52 PM, Lee, Yiu wrote:
>>>>> Hi Carsten,
>>>>>
>>>>> Thanks very much for reviewing the document. I just want to add a
>>>>> point
>>>>> to
>>>>> your question about how applications decide when to use this multicast
>>>>> address format. In fact, they don't. Imagine a use case where a legacy
>>>>> IPv4 IP-TV receiver (an app) wants to join a channel which is
>>>>> broadcasted
>>>>> in IPv6. The app will continue to send the igmp-join (say 224.1.2.3).
>>>> How does the IPv4 IP-TV know to join 224.1.2.3?
>>>>
>>>> How is 224.1.2.3 advertised to the IPv4 IP-TV clients if the content is
>>>> generated by an IPv6 source?  Does the source need to be configured to
>>>> use one of these IPv4-in-IPv6 multicast addresses?
>>>>
>>>>> There will be a function in the network which is statically configured
>>>>> that when it receives a igmp-join, it would covert to a corresponding
>>>>> mld-join. The IPv6 address in the join message will follow what is
>>>>> described in this draft. This Adaptive Function is transparent to the
>>>>> application and managed by the network.
>>>> Are you limiting this approach to only mapping at the IGMP/MLD
>>>> protocols?
>>>>
>>>> How does your Adaptive Function know which IPv6 multicast prefix to use
>>>> when mapping the IPv4 multicast address in the IGMP Report message to
>>>> MLD?
>>>>
>>>> Regards,
>>>> Brian
>>
>>
>> _______________________________________________
>> MBONED mailing list
>> MBONED@ietf.org
>> https://www.ietf.org/mailman/listinfo/mboned

--------------090903050302090805080501
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">
    <font face="Calibri">Re-,<br>
    </font><br>
    On 5/15/2012 Tuesday 5:06 AM, Lee, Yiu wrote:
    <blockquote cite="mid:CBD6EB81.20E9E%25yiu_lee@cable.comcast.com"
      type="cite">
      <pre wrap="">Hi Stig,

Right. I explain only one use case. Other may find the latter case is more
attractive for their deployments. This address format should enable the
dynamic use case as well.
</pre>
    </blockquote>
    Yes, imaging the coexistence of the native provisioning and the
    embedded address for some transition approach deployment, to perform
    that statelessly, a flag bit is efficient.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <blockquote cite="mid:CBD6EB81.20E9E%25yiu_lee@cable.comcast.com"
      type="cite">
      <pre wrap="">
Yiu

On 5/14/12 4:56 PM, "Stig Venaas" <a class="moz-txt-link-rfc2396E" href="mailto:stig@cisco.com">&lt;stig@cisco.com&gt;</a> wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">On 5/14/2012 1:50 PM, Lee, Yiu wrote:
</pre>
        <blockquote type="cite">
          <pre wrap="">Hi Brian,

Sorry for getting back late. I read Bert's answers to your questions.
His
answers are inline with my answers. Most information are statically
configured. For example: Ch1 is statically configured to 224.1.2.3 via
OOB
mechanism. If the STB is IPv4 only, it will only use IPv4 mcast address.
It won't use the address format defined in this draft. In my mind, the
most common deployment will use the same IPv6 prefix which will be
statically configured in the AF.
</pre>
        </blockquote>
        <pre wrap="">
Right, so that was my main concern with the draft. Is static
configuration like this sufficient, or are there more generic cases
where one needs to know that it is translated from IPv4 without a
priori configuration. The flag bit (or a well-known prefix) is only
needed in the latter case. I know there were some scenarios where
someone found the latter to be advantageous though.

Stig

</pre>
        <blockquote type="cite">
          <pre wrap="">
Regards,
Yiu


On 5/10/12 2:03 PM, "Brian Haberman"<a class="moz-txt-link-rfc2396E" href="mailto:brian@innovationslab.net">&lt;brian@innovationslab.net&gt;</a>  wrote:

</pre>
          <blockquote type="cite">
            <pre wrap="">Hi Yiu,
      Let me ask a few questions...

On 5/9/12 10:52 PM, Lee, Yiu wrote:
</pre>
            <blockquote type="cite">
              <pre wrap="">Hi Carsten,

Thanks very much for reviewing the document. I just want to add a
point
to
your question about how applications decide when to use this multicast
address format. In fact, they don't. Imagine a use case where a legacy
IPv4 IP-TV receiver (an app) wants to join a channel which is
broadcasted
in IPv6. The app will continue to send the igmp-join (say 224.1.2.3).
</pre>
            </blockquote>
            <pre wrap="">
How does the IPv4 IP-TV know to join 224.1.2.3?

How is 224.1.2.3 advertised to the IPv4 IP-TV clients if the content is
generated by an IPv6 source?  Does the source need to be configured to
use one of these IPv4-in-IPv6 multicast addresses?

</pre>
            <blockquote type="cite">
              <pre wrap="">There will be a function in the network which is statically configured
that when it receives a igmp-join, it would covert to a corresponding
mld-join. The IPv6 address in the join message will follow what is
described in this draft. This Adaptive Function is transparent to the
application and managed by the network.
</pre>
            </blockquote>
            <pre wrap="">
Are you limiting this approach to only mapping at the IGMP/MLD
protocols?

How does your Adaptive Function know which IPv6 multicast prefix to use
when mapping the IPv4 multicast address in the IGMP Report message to
MLD?

Regards,
Brian
</pre>
          </blockquote>
        </blockquote>
        <pre wrap="">
</pre>
        <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>
    </blockquote>
  </body>
</html>

--------------090903050302090805080501--


From tom.taylor.stds@gmail.com  Wed May 16 18:08:00 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 C5C1321F858A for <mboned@ietfa.amsl.com>; Wed, 16 May 2012 18:08:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.481
X-Spam-Level: 
X-Spam-Status: No, score=-3.481 tagged_above=-999 required=5 tests=[AWL=0.118,  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 L3AQ+nQo+6ue for <mboned@ietfa.amsl.com>; Wed, 16 May 2012 18:08:00 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id DFFEF21F8589 for <mboned@ietf.org>; Wed, 16 May 2012 18:07:59 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so1092998lbb.31 for <mboned@ietf.org>; Wed, 16 May 2012 18:07:58 -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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-antivirus:x-antivirus-status; bh=/pMk/X6ua0+ByZoSRdUiV9XWprB0aBU+zz6RR3P9UeI=; b=sDVEnSt1J+NiJkMXiIBvbOvyidl0PX5XaHYiNucjTAIxoIcUo0VVWj9tUEP09U3Vwn EkI44PWXKZDDiKmCSqIzQzOHXcT6m/3nZwrCe06TPMJegjwntO+VZuR6pO4eiZwvnNyq Es7bQMllIQDsiDKD1a6YN90bUC88H9lIT79n7rrhh+C2495Sy/kqLEuF9j7cEjy18AdI j+b5/QkAk58L/w3xWq0bI+bPpfUlhJKlUgLGJZCAGLs32iDcK+VPfYpXPZ/Rvf75vT+J NCgR7CArM62RFtdYwZ80vfo9cQAKnMM8Ldd9TSqMPeOWdyIJbp8YfZrH4ZGE6XaRbwzM MG5A==
Received: by 10.112.100.7 with SMTP id eu7mr2141917lbb.105.1337216878687; Wed, 16 May 2012 18:07:58 -0700 (PDT)
Received: from [127.0.0.1] (dsl-207-112-91-137.tor.primus.ca. [207.112.91.137]) by mx.google.com with ESMTPS id lv13sm5483970lab.8.2012.05.16.18.07.55 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 16 May 2012 18:07:57 -0700 (PDT)
Message-ID: <4FB44F66.5020604@gmail.com>
Date: Wed, 16 May 2012 21:07:50 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Leonard Giuliano <lenny@juniper.net>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com> <20120514132102.U91557@eng-mail01.juniper.net>
In-Reply-To: <20120514132102.U91557@eng-mail01.juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120516-1, 16/05/2012), Outbound message
X-Antivirus-Status: Clean
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 17 May 2012 01:08:00 -0000

I believe the subject draft should be adopted as a work item. In 
response to Jacni Qin, I note that the absence of such a document led to 
extensive discussion of the topic in the interim meeting, despite its 
treatment in the problem statement draft. This, I think, is a clear 
indication that something more had to be said.


The question of whether receiver modification is in scope has come up in 
prior discussion. I think there should be a clear statement of the 
following in the introduction to the draft:

(1) The most straightforward solution to the acquisition problem is to 
make receivers dual-stack. That is, the receiver can extract IP 
addresses from the EPG regardless of their version and join and leave 
streams using either IGMP/IPv4 or MLD/IPv6 depending on the supplied 
addresses.

(2) Any solution that involves more costly changes to the receiver than 
making it dual-stack as just defined is therefore probably uneconomic.

This is why the degree of receiver modification required is a 
consideration for the different solution approaches.


One final remark: the current version of the draft doesn't necessarily 
cover all the possibilities, and one would hope the WG might add input 
to make it more inclusive. But it is probably a good start.

Tom Taylor

From jacni@jacni.com  Wed May 16 20:15:49 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 1794F11E8073 for <mboned@ietfa.amsl.com>; Wed, 16 May 2012 20:15:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level: 
X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[AWL=0.267,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=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 eOBYlmulWl82 for <mboned@ietfa.amsl.com>; Wed, 16 May 2012 20:15:48 -0700 (PDT)
Received: from srv05.olivemail.cn (mx100.vip.olivemail.net [74.82.185.218]) by ietfa.amsl.com (Postfix) with ESMTP id 7144F21F86BE for <mboned@ietf.org>; Wed, 16 May 2012 20:15:47 -0700 (PDT)
Received: from srv01.olivemail.cn (unknown [202.105.21.229]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by srv05.olivemail.cn (Olivemail) with ESMTPS id 4670B3800BD for <mboned@ietf.org>; Wed, 16 May 2012 23:15:46 -0400 (EDT)
Received: from oray.cn (unknown [202.105.21.248]) by srv01.olivemail.cn (Olivemail) with ESMTP id BBA953400A8 for <mboned@ietf.org>; Thu, 17 May 2012 11:15:44 +0800 (CST)
Received: from [10.79.99.107] (unknown [64.104.125.217]) by app (Coremail) with SMTP id +AWowJD7L41cbbRPFF33AA--.33254S2; Thu, 17 May 2012 11:15:41 +0800 (CST)
Message-ID: <4FB46D58.4060003@jacni.com>
Date: Thu, 17 May 2012 11:15:36 +0800
From: Jacni Qin <jacni@jacni.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Tom Taylor <tom.taylor.stds@gmail.com>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com> <20120514132102.U91557@eng-mail01.juniper.net> <4FB44F66.5020604@gmail.com>
In-Reply-To: <4FB44F66.5020604@gmail.com>
Content-Type: multipart/alternative; boundary="------------030705000806070000080408"
X-CM-TRANSID: +AWowJD7L41cbbRPFF33AA--.33254S2
X-Coremail-Antispam: 1UD129KBjvJXoW7CF1rWFWfJrWfKF1UZF48Crg_yoW8AFyUpF W7CF47GF1kJ3W7Gas7X3WFqFyYkFyktFWUArnxKr1UA34Yga40qFyUK3y5CrWDWr4FvF12 vr129rs8Ga4Sv3DanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnL8YjsxI4VWxJwAYFVCjjxCrM7CY07I20VC2zVCF04k26cxKx2IYs7xG 6rWj6s0DMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8JwACjcxG0x vEwIxGrwCjr7xvwVCIw2I0I7xG6c02F41lc7I2V7IY0VAS07AlzVAYIcxG8wCF04k20xvY 0x0EwIxGrwC2zVAF1VAY17CE14v26r1Y6r17MIIYrxkI7VAKI48JYxBIdaVFxhVjvjDU0x ZFpf9x07jDnYwUUUUU=
X-CM-SenderInfo: xmdf0xo6mdu03lof0z/1tbiAQEQEko7lRAv0QAKsC
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 17 May 2012 03:15:49 -0000

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

hi,

On 5/17/2012 Thursday 9:07 AM, Tom Taylor wrote:
> I believe the subject draft should be adopted as a work item. In
> response to Jacni Qin, I note that the absence of such a document led
> to extensive discussion of the topic in the interim meeting, despite
> its treatment in the problem statement draft. This, I think, is a
> clear indication that something more had to be said.
>
Except for the extension mentioned in the second approach of 3.3, I
still can't see anything new than what have been discussed in the
Section 4 of Problem Statement,
http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00#page-18


>
> The question of whether receiver modification is in scope has come up
> in prior discussion. 
Thanks for the information.


Cheers,
Jacni


> I think there should be a clear statement of the following in the
> introduction to the draft:
>
> (1) The most straightforward solution to the acquisition problem is to
> make receivers dual-stack. That is, the receiver can extract IP
> addresses from the EPG regardless of their version and join and leave
> streams using either IGMP/IPv4 or MLD/IPv6 depending on the supplied
> addresses.
>
> (2) Any solution that involves more costly changes to the receiver
> than making it dual-stack as just defined is therefore probably
> uneconomic.
>
> This is why the degree of receiver modification required is a
> consideration for the different solution approaches.
>
>
> One final remark: the current version of the draft doesn't necessarily
> cover all the possibilities, and one would hope the WG might add input
> to make it more inclusive. But it is probably a good start.
>
> Tom Taylor
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>
>

--------------030705000806070000080408
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=GB2312" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Calibri">hi,</font><br>
    <br>
    On 5/17/2012 Thursday 9:07 AM, Tom Taylor wrote:
    <blockquote cite="mid:4FB44F66.5020604@gmail.com" type="cite">I
      believe the subject draft should be adopted as a work item. In
      response to Jacni Qin, I note that the absence of such a document
      led to extensive discussion of the topic in the interim meeting,
      despite its treatment in the problem statement draft. This, I
      think, is a clear indication that something more had to be said.
      <br>
      <br>
    </blockquote>
    Except for the extension mentioned in the second approach of 3.3, I
    still can't see anything new than what have been discussed in the
    Section 4 of Problem Statement,
    <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00#page-18">http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00#page-18</a><br>
    <br>
    <br>
    <blockquote cite="mid:4FB44F66.5020604@gmail.com" type="cite">
      <br>
      The question of whether receiver modification is in scope has come
      up in prior discussion. </blockquote>
    Thanks for the information.<br>
    <br>
    <br>
    Cheers,<br>
    Jacni<br>
    <br>
    <br>
    <blockquote cite="mid:4FB44F66.5020604@gmail.com" type="cite">I
      think there should be a clear statement of the following in the
      introduction to the draft:
      <br>
      <br>
      (1) The most straightforward solution to the acquisition problem
      is to make receivers dual-stack. That is, the receiver can extract
      IP addresses from the EPG regardless of their version and join and
      leave streams using either IGMP/IPv4 or MLD/IPv6 depending on the
      supplied addresses.
      <br>
      <br>
      (2) Any solution that involves more costly changes to the receiver
      than making it dual-stack as just defined is therefore probably
      uneconomic.
      <br>
      <br>
      This is why the degree of receiver modification required is a
      consideration for the different solution approaches.
      <br>
      <br>
      <br>
      One final remark: the current version of the draft doesn't
      necessarily cover all the possibilities, and one would hope the WG
      might add input to make it more inclusive. But it is probably a
      good start.
      <br>
      <br>
      Tom Taylor
      <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>
  </body>
</html>

--------------030705000806070000080408--


From internet-drafts@ietf.org  Thu May 17 11:15:23 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 AA3A721F8726; Thu, 17 May 2012 11:15: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=[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 s6UsrpdX19Xv; Thu, 17 May 2012 11:15:23 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C513B21F86FF; Thu, 17 May 2012 11:15:22 -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.02
Message-ID: <20120517181522.29906.13728.idtracker@ietfa.amsl.com>
Date: Thu, 17 May 2012 11:15:22 -0700
Cc: mboned@ietf.org
Subject: [MBONED] I-D Action: draft-ietf-mboned-mcaddrdoc-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: Thu, 17 May 2012 18:15:23 -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=
 IETF.

	Title           : Multicast Addresses for Documentation
	Author(s)       : Stig Venaas
                          Rishabh Parekh
                          Gunter Van de Velde
                          Tim Chown
                          Marshall Eubanks
	Filename        : draft-ietf-mboned-mcaddrdoc-04.txt
	Pages           : 13
	Date            : 2012-05-17

   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.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mboned-mcaddrdoc-04.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mboned-mcaddrdoc-04.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-mboned-mcaddrdoc/


From gjshep@gmail.com  Mon May 21 12:30:56 2012
Return-Path: <gjshep@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 95F0621F859A for <mboned@ietfa.amsl.com>; Mon, 21 May 2012 12:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60jApXcJAwZJ for <mboned@ietfa.amsl.com>; Mon, 21 May 2012 12:30:56 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id AB2A221F84A1 for <mboned@ietf.org>; Mon, 21 May 2012 12:30:55 -0700 (PDT)
Received: by bkty8 with SMTP id y8so5188242bkt.31 for <mboned@ietf.org>; Mon, 21 May 2012 12:30:54 -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; bh=eBtBsg/gVZyNZO9AtHRqa0TErdrAxvnIgNOc1sUlkIc=; b=eykKfIgf+QwYohwL9mHxuTmWjRQuwIo0sRL+kP8yMh4oqsXw/rlVOVvU+ADrvYNby7 XuL01uzH/NJ73j4VcIyhY+lKKdx9n4Qd/OY77zf202wjBjSSIw2VrveBFVOSMzDrrRFO 7v2nLN0k6PuV0Moa3zQ6Q9djq3iEet+rAaKnA3trPV3r5ObGQv6s7xDR3ytckzOa9V8y HoAdjAL+ueUMHyqwF/hKoDVccr6XbCm69WnrwMkxbDF84sYFzjut2lsE66mDumMJQWhp dD6dOAIjzNplZdQNUuaH88KOdsKPX/sbGOOVOR0mmv186aG2pTfU2AnWLYBJVfmqZRQ7 Se2A==
MIME-Version: 1.0
Received: by 10.204.149.216 with SMTP id u24mr8284610bkv.36.1337628654785; Mon, 21 May 2012 12:30:54 -0700 (PDT)
Received: by 10.204.68.13 with HTTP; Mon, 21 May 2012 12:30:54 -0700 (PDT)
In-Reply-To: <CABFReBqo43QsBWwu=_nbDgw-eoK1S2+8xszTXY1Zm=KLhmvRPA@mail.gmail.com>
References: <CABFReBqo43QsBWwu=_nbDgw-eoK1S2+8xszTXY1Zm=KLhmvRPA@mail.gmail.com>
Date: Mon, 21 May 2012 12:30:54 -0700
Message-ID: <CABFReBof8GKz=yzmPxLGk+eTsUE20PYvZOyO9fqMcY8oFcwnow@mail.gmail.com>
From: Greg Shepherd <gjshep@gmail.com>
To: mboned@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gjshep@gmail.com
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, 21 May 2012 19:30:56 -0000

We're half way through the 3 week WGLC for AMT and we've received no
responses. Please read and respond ASAP so we can progress.

Thanks,
Greg

On Thu, May 10, 2012 at 10:33 AM, Greg Shepherd <gjshep@gmail.com> wrote:
> *,
>
> Yes, I think we may finally be here! The Paris and post-Paris
> discussions were addressed in the finally rev so it is now time for
> WGLC for draft-ietf-mboned-auto-multicast-13:
>
> https://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast/
>
> It is quite long so we'll give it three weeks for responses before
> moving it along. Please respond by May 31st. And as always, we need
> votes of approval as much as comments and issues. Let's see this
> finally move to req pub!
>
> Thanks to everyone who has been involved throughout the past +decade. :p
>
> MBONED Chairs

From gjshep@gmail.com  Mon May 21 13:18:52 2012
Return-Path: <gjshep@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 E235D21F8597 for <mboned@ietfa.amsl.com>; Mon, 21 May 2012 13:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sBe1jRZQ1XbX for <mboned@ietfa.amsl.com>; Mon, 21 May 2012 13:18:52 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 19EC221F8569 for <mboned@ietf.org>; Mon, 21 May 2012 13:18:51 -0700 (PDT)
Received: by bkty8 with SMTP id y8so5228572bkt.31 for <mboned@ietf.org>; Mon, 21 May 2012 13:18:51 -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:content-transfer-encoding; bh=eA55j6avlHuxibYWGIRcyFfz3vEqYfvFiyNyrvGqF8U=; b=QAaOabqb60gk4qfxmgowaBGJjmT2oUiMXgHzHucWOIFvG5HFBtwPlcg1d1OQLgIjSs 6edwp4uywkHguoVD5dcc5JNi9jB42nK5mPfOleDDIfb/K6JgfBgGJUBZ3/LXHRb7wgAk nk8QdJ1llYClF3Ni0AgQBhn+Ha8ODsppBinPdtHSkUMcCUjGxgXtLh1F7gGbRWTDVZ6D fvefKG3V9rieqyzyy/D027xgFJ7ADZ9qWcue3yQpJBip3hkojrkbiJLRb4nYH2r/V+Lk fi5fDOFS8yUNwOC83O0Mfkt3BCeM0DaOGvnixNYj6dg3l/5b90NhKQYbqxZ7lbyWkCAK ZNbg==
MIME-Version: 1.0
Received: by 10.204.153.6 with SMTP id i6mr8243521bkw.114.1337631531172; Mon, 21 May 2012 13:18:51 -0700 (PDT)
Received: by 10.204.68.13 with HTTP; Mon, 21 May 2012 13:18:51 -0700 (PDT)
In-Reply-To: <9B30768B8155174FB7C6B21ABDCD24C001D687E5@GAALPA1MSGUSR9N.ITServices.sbc.com>
References: <Ac0SYcs7k5DhJOMpQS+JiCq8D7XSMQ==> <9B30768B8155174FB7C6B21ABDCD24C001D687E5@GAALPA1MSGUSR9N.ITServices.sbc.com>
Date: Mon, 21 May 2012 13:18:51 -0700
Message-ID: <CABFReBqi9u914gcMsYBPTCEubv=m0KgGmdkG1j6Teco_ELSTUw@mail.gmail.com>
From: Greg Shepherd <gjshep@gmail.com>
To: "SAYKO, ROBERT J" <rs1983@att.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] Interdomain/AS Multicast for CDN
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gjshep@gmail.com
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, 21 May 2012 20:18:53 -0000

Inline:

On Wed, Apr 4, 2012 at 5:52 AM, SAYKO, ROBERT J <rs1983@att.com> wrote:
>
> All,
>
>
> As we didn't have time to complete our agenda on last Thursday I didn't h=
ave the opportunity to raise this topic.
>
> (As I am very new to IETF please excuse me if I am not following correct =
protocol or process in the following)
>
> I would like to propose that mboned initiate work on a draft for Inter-do=
main/AS CDN Multicast. =A0I have already spoken
> with one of our chairs, =A0Greg Shepherd, on this and he indicated that h=
e would support the WG taking it on.

And I still think this is appropriate work for MBONED.

> I am aware that CDNi is doing a lot of interdomain CDN work, =A0but they =
are not addressing multicast and per their
> chairs do not want to take on multicast at this time (or from what I gath=
er in the near future). =A0 =A0I have recently
> completed work on the ATIS interdomain MC specification and would like to=
 take that work as a starting point to go
> even further by creating a RFC through IETF.

This seems to be the typical response in the IETF and why MBONED has
become the mcast safety net. Additionally, this isn't protocol work so
it fits right into our charter.

> If mboned takes on this challenge I think our scope will be slightly diff=
erent then if CDNi were to do it, =A0but that is fine
> and it would not be demonstratively different I think. =A0 Since I think =
interdomain CDN MC is almost a niche I think it
> would actually be easier to do then the caching based approach CDNi seems=
 to be concentrating on.

Agreed.

> Interdomain CDNi is also likely to be more quickly and incorporated by so=
me large operators then cache based. =A0There
> are a number of reasons for this: =A0many operators have MC ready or oper=
ating backbones, =A0it is a quick starter, =A0MC
> ready content is rapidly growing, =A0less investment then cache, =A0best =
solution for flash crowds. =A0Also, =A0large operators
> have within their ownership several AS's with separate CDNs in some cases=
 and see MC as an extremely significant
> cost saving technology.

>From the WGs perspective, you've done the hard bit already in ATIS. We
just need to advance this work in the IETF, possibly as a BCP draft.

> Hopefully, =A0the WG will favorably consider taking this on. =A0I would b=
e happy to be lead author, =A0but would of course like
> as much help as possible. =A0Please give me your comments and questions.

Again, I'm all for it. Anyone on the list interested in helping Bob
author the draft?

Thanks!,
Greg

> Regards,
> Bob Sayko
>
>
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From Tina.Tsou.Zouting@huawei.com  Mon May 21 14:02:30 2012
Return-Path: <Tina.Tsou.Zouting@huawei.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 4643021F855A for <mboned@ietfa.amsl.com>; Mon, 21 May 2012 14:02:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.996
X-Spam-Level: 
X-Spam-Status: No, score=-4.996 tagged_above=-999 required=5 tests=[AWL=1.603,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 cUxHPhahvivZ for <mboned@ietfa.amsl.com>; Mon, 21 May 2012 14:02:29 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 0CDCB21F8597 for <mboned@ietf.org>; Mon, 21 May 2012 14:02:29 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AGC99329; Mon, 21 May 2012 17:02:26 -0400 (EDT)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 21 May 2012 13:59:46 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.80]) by dfweml406-hub.china.huawei.com ([10.193.5.131]) with mapi id 14.01.0323.003; Mon, 21 May 2012 13:59:45 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: "gjshep@gmail.com" <gjshep@gmail.com>, "SAYKO, ROBERT J" <rs1983@att.com>
Thread-Topic: [MBONED] Interdomain/AS Multicast for CDN
Thread-Index: AQHNN47+EZAqqjXrAEewEFosPKNa+JbUuIlg
Date: Mon, 21 May 2012 20:59:45 +0000
Message-ID: <C0E0A32284495243BDE0AC8A066631A80D395E48@dfweml513-mbx.china.huawei.com>
References: <Ac0SYcs7k5DhJOMpQS+JiCq8D7XSMQ==> <9B30768B8155174FB7C6B21ABDCD24C001D687E5@GAALPA1MSGUSR9N.ITServices.sbc.com> <CABFReBqi9u914gcMsYBPTCEubv=m0KgGmdkG1j6Teco_ELSTUw@mail.gmail.com>
In-Reply-To: <CABFReBqi9u914gcMsYBPTCEubv=m0KgGmdkG1j6Teco_ELSTUw@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.193.216.177]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] Interdomain/AS Multicast for CDN
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, 21 May 2012 21:02:30 -0000

Is it related to CDNi WG as well?

Tina

> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf
> Of Greg Shepherd
> Sent: Monday, May 21, 2012 1:19 PM
> To: SAYKO, ROBERT J
> Cc: mboned@ietf.org
> Subject: Re: [MBONED] Interdomain/AS Multicast for CDN
>=20
> Inline:
>=20
> On Wed, Apr 4, 2012 at 5:52 AM, SAYKO, ROBERT J <rs1983@att.com> wrote:
> >
> > All,
> >
> >
> > As we didn't have time to complete our agenda on last Thursday I didn't
> have the opportunity to raise this topic.
> >
> > (As I am very new to IETF please excuse me if I am not following correc=
t
> protocol or process in the following)
> >
> > I would like to propose that mboned initiate work on a draft for Inter-
> domain/AS CDN Multicast. =A0I have already spoken
> > with one of our chairs, =A0Greg Shepherd, on this and he indicated that=
 he
> would support the WG taking it on.
>=20
> And I still think this is appropriate work for MBONED.
>=20
> > I am aware that CDNi is doing a lot of interdomain CDN work, =A0but the=
y
> are not addressing multicast and per their
> > chairs do not want to take on multicast at this time (or from what I
> gather in the near future). =A0 =A0I have recently
> > completed work on the ATIS interdomain MC specification and would like
> to take that work as a starting point to go
> > even further by creating a RFC through IETF.
>=20
> This seems to be the typical response in the IETF and why MBONED has
> become the mcast safety net. Additionally, this isn't protocol work so
> it fits right into our charter.
>=20
> > If mboned takes on this challenge I think our scope will be slightly
> different then if CDNi were to do it, =A0but that is fine
> > and it would not be demonstratively different I think. =A0 Since I thin=
k
> interdomain CDN MC is almost a niche I think it
> > would actually be easier to do then the caching based approach CDNi
> seems to be concentrating on.
>=20
> Agreed.
>=20
> > Interdomain CDNi is also likely to be more quickly and incorporated by
> some large operators then cache based. =A0There
> > are a number of reasons for this: =A0many operators have MC ready or
> operating backbones, =A0it is a quick starter, =A0MC
> > ready content is rapidly growing, =A0less investment then cache, =A0bes=
t
> solution for flash crowds. =A0Also, =A0large operators
> > have within their ownership several AS's with separate CDNs in some
> cases and see MC as an extremely significant
> > cost saving technology.
>=20
> From the WGs perspective, you've done the hard bit already in ATIS. We
> just need to advance this work in the IETF, possibly as a BCP draft.
>=20
> > Hopefully, =A0the WG will favorably consider taking this on. =A0I would=
 be
> happy to be lead author, =A0but would of course like
> > as much help as possible. =A0Please give me your comments and questions=
.
>=20
> Again, I'm all for it. Anyone on the list interested in helping Bob
> author the draft?
>=20
> Thanks!,
> Greg
>=20
> > Regards,
> > Bob Sayko
> >
> >
> > _______________________________________________
> > 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 rs1983@att.com  Mon May 21 14:34:08 2012
Return-Path: <rs1983@att.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 102D821F851A for <mboned@ietfa.amsl.com>; Mon, 21 May 2012 14:34:08 -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 R-EnrR+hRCCt for <mboned@ietfa.amsl.com>; Mon, 21 May 2012 14:34:07 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) by ietfa.amsl.com (Postfix) with ESMTP id 1A19A21F8551 for <mboned@ietf.org>; Mon, 21 May 2012 14:34:07 -0700 (PDT)
Received: from unknown [144.160.20.146] (EHLO nbfkord-smmo07.seg.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.11.0-10) with ESMTP id fc4babf4.7325b940.1138143.00-578.3095590.nbfkord-smmo07.seg.att.com (envelope-from <rs1983@att.com>);  Mon, 21 May 2012 21:34:07 +0000 (UTC)
X-MXL-Hash: 4fbab4cf2331ac45-0844b5abf2b104bed1f10e94532f4bdaf69d4fd5
Received: from unknown [144.160.20.146] (EHLO mlpd194.enaf.sfdc.sbc.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id 7c4babf4.0.1138120.00-413.3095532.nbfkord-smmo07.seg.att.com (envelope-from <rs1983@att.com>);  Mon, 21 May 2012 21:33:59 +0000 (UTC)
X-MXL-Hash: 4fbab4c749c61ddf-690e1b5993e9aa961cad55771a6d50ec1b54d5ca
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q4LLXwoW013179; Mon, 21 May 2012 17:33:58 -0400
Received: from sflint03.pst.cso.att.com (sflint03.pst.cso.att.com [144.154.234.230]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q4LLXO8d012597 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 May 2012 17:33:51 -0400
Received: from GAALPA1MSGHUB9B.ITServices.sbc.com (gaalpa1msghub9b.itservices.sbc.com [130.8.36.88]) by sflint03.pst.cso.att.com (RSA Interceptor); Mon, 21 May 2012 17:32:45 -0400
Received: from GAALPA1MSGUSR9N.ITServices.sbc.com ([130.8.36.71]) by GAALPA1MSGHUB9B.ITServices.sbc.com ([130.8.36.88]) with mapi id 14.01.0355.002; Mon, 21 May 2012 17:32:44 -0400
From: "SAYKO, ROBERT J" <rs1983@att.com>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>, "gjshep@gmail.com" <gjshep@gmail.com>
Thread-Topic: [MBONED] Interdomain/AS Multicast for CDN
Thread-Index: AQHNN471CWf4iYkAj0+No7eQqMoznZbU/T2A//+95QA=
Date: Mon, 21 May 2012 21:32:43 +0000
Message-ID: <9B30768B8155174FB7C6B21ABDCD24C001DC2BE0@GAALPA1MSGUSR9N.ITServices.sbc.com>
References: <Ac0SYcs7k5DhJOMpQS+JiCq8D7XSMQ==> <9B30768B8155174FB7C6B21ABDCD24C001D687E5@GAALPA1MSGUSR9N.ITServices.sbc.com> <CABFReBqi9u914gcMsYBPTCEubv=m0KgGmdkG1j6Teco_ELSTUw@mail.gmail.com> <C0E0A32284495243BDE0AC8A066631A80D395E48@dfweml513-mbx.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80D395E48@dfweml513-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.187.205]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <rs1983@att.com>
X-SOURCE-IP: [144.160.20.146]
X-AnalysisOut: [v=1.0 c=1 a=kIIE2rl2P-oA:10 a=xdcERly8WI4A:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:10 a=Qs8R1XBwmid1qB]
X-AnalysisOut: [FB/a8mmA==:17 a=i0EeH86SAAAA:8 a=pGLkceISAAAA:8 a=48vgC7mU]
X-AnalysisOut: [AAAA:8 a=zQP7CpKOAAAA:8 a=X5f2utlMRi2UT1uL7OUA:9 a=2HK3ySw]
X-AnalysisOut: [JCJeGPkG4wckA:7 a=wPNLvfGTeEIA:10 a=hPjdaMEvmhQA:10 a=MSl-]
X-AnalysisOut: [tDqOz04A:10 a=lZB815dzVvQA:10 a=Hz7IrDYlS0cA:10 a=_5Ri5zKj]
X-AnalysisOut: [bkPOayXY:21 a=KiZ5kJu3JxlqEmd_:21]
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] Interdomain/AS Multicast for CDN
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, 21 May 2012 21:34:08 -0000

It is related in that it will identify the type of underlying/basic procedu=
res and components for interdomain MC be it native or AMT.  So in a way it =
is similar what CDNi is doing with caching in that respect. Like Greg said =
I don't think this will entail protocol work,  unless perhaps utilizing exi=
sting protocol parameters (e.g. or perhaps adding new value to a parameter)=
 implies protocol work.    =20

-----Original Message-----
From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]=20
Sent: Monday, May 21, 2012 5:00 PM
To: gjshep@gmail.com; SAYKO, ROBERT J
Cc: mboned@ietf.org
Subject: RE: [MBONED] Interdomain/AS Multicast for CDN

Is it related to CDNi WG as well?

Tina

> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf
> Of Greg Shepherd
> Sent: Monday, May 21, 2012 1:19 PM
> To: SAYKO, ROBERT J
> Cc: mboned@ietf.org
> Subject: Re: [MBONED] Interdomain/AS Multicast for CDN
>=20
> Inline:
>=20
> On Wed, Apr 4, 2012 at 5:52 AM, SAYKO, ROBERT J <rs1983@att.com> wrote:
> >
> > All,
> >
> >
> > As we didn't have time to complete our agenda on last Thursday I didn't
> have the opportunity to raise this topic.
> >
> > (As I am very new to IETF please excuse me if I am not following correc=
t
> protocol or process in the following)
> >
> > I would like to propose that mboned initiate work on a draft for Inter-
> domain/AS CDN Multicast. =A0I have already spoken
> > with one of our chairs, =A0Greg Shepherd, on this and he indicated that=
 he
> would support the WG taking it on.
>=20
> And I still think this is appropriate work for MBONED.
>=20
> > I am aware that CDNi is doing a lot of interdomain CDN work, =A0but the=
y
> are not addressing multicast and per their
> > chairs do not want to take on multicast at this time (or from what I
> gather in the near future). =A0 =A0I have recently
> > completed work on the ATIS interdomain MC specification and would like
> to take that work as a starting point to go
> > even further by creating a RFC through IETF.
>=20
> This seems to be the typical response in the IETF and why MBONED has
> become the mcast safety net. Additionally, this isn't protocol work so
> it fits right into our charter.
>=20
> > If mboned takes on this challenge I think our scope will be slightly
> different then if CDNi were to do it, =A0but that is fine
> > and it would not be demonstratively different I think. =A0 Since I thin=
k
> interdomain CDN MC is almost a niche I think it
> > would actually be easier to do then the caching based approach CDNi
> seems to be concentrating on.
>=20
> Agreed.
>=20
> > Interdomain CDNi is also likely to be more quickly and incorporated by
> some large operators then cache based. =A0There
> > are a number of reasons for this: =A0many operators have MC ready or
> operating backbones, =A0it is a quick starter, =A0MC
> > ready content is rapidly growing, =A0less investment then cache, =A0bes=
t
> solution for flash crowds. =A0Also, =A0large operators
> > have within their ownership several AS's with separate CDNs in some
> cases and see MC as an extremely significant
> > cost saving technology.
>=20
> From the WGs perspective, you've done the hard bit already in ATIS. We
> just need to advance this work in the IETF, possibly as a BCP draft.
>=20
> > Hopefully, =A0the WG will favorably consider taking this on. =A0I would=
 be
> happy to be lead author, =A0but would of course like
> > as much help as possible. =A0Please give me your comments and questions=
.
>=20
> Again, I'm all for it. Anyone on the list interested in helping Bob
> author the draft?
>=20
> Thanks!,
> Greg
>=20
> > Regards,
> > Bob Sayko
> >
> >
> > _______________________________________________
> > 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 rs1983@att.com  Mon May 21 14:34:51 2012
Return-Path: <rs1983@att.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 0624D21F8493 for <mboned@ietfa.amsl.com>; Mon, 21 May 2012 14:34:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=2.000, 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 x6MdA94o-t8S for <mboned@ietfa.amsl.com>; Mon, 21 May 2012 14:34:50 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id 30E6521F845B for <mboned@ietf.org>; Mon, 21 May 2012 14:34:50 -0700 (PDT)
Received: from unknown [144.160.20.146] (EHLO nbfkord-smmo06.seg.att.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.11.0-10) with ESMTP id af4babf4.54e33940.332236.00-583.908290.nbfkord-smmo06.seg.att.com (envelope-from <rs1983@att.com>);  Mon, 21 May 2012 21:34:50 +0000 (UTC)
X-MXL-Hash: 4fbab4fa0422d66c-c88773a7afa523f3918d399a4268dd15d32f647a
Received: from unknown [144.160.20.146] (EHLO mlpd194.enaf.sfdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id 1f4babf4.0.332191.00-497.908173.nbfkord-smmo06.seg.att.com (envelope-from <rs1983@att.com>);  Mon, 21 May 2012 21:34:42 +0000 (UTC)
X-MXL-Hash: 4fbab4f214b8d4d1-bb73d70712e4e9b378dfc703575e78642ae3acf2
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q4LLYes4013976; Mon, 21 May 2012 17:34:41 -0400
Received: from sflint03.pst.cso.att.com (sflint03.pst.cso.att.com [144.154.234.230]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q4LLYYVo013811 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 May 2012 17:34:36 -0400
Received: from GAALPA1MSGHUB9B.ITServices.sbc.com (gaalpa1msghub9b.itservices.sbc.com [130.8.36.88]) by sflint03.pst.cso.att.com (RSA Interceptor); Mon, 21 May 2012 17:34:11 -0400
Received: from GAALPA1MSGUSR9N.ITServices.sbc.com ([130.8.36.71]) by GAALPA1MSGHUB9B.ITServices.sbc.com ([130.8.36.88]) with mapi id 14.01.0355.002; Mon, 21 May 2012 17:34:11 -0400
From: "SAYKO, ROBERT J" <rs1983@att.com>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>, "gjshep@gmail.com" <gjshep@gmail.com>
Thread-Topic: [MBONED] Interdomain/AS Multicast for CDN
Thread-Index: AQHNN471CWf4iYkAj0+No7eQqMoznZbU/T2A///GPrA=
Date: Mon, 21 May 2012 21:34:11 +0000
Message-ID: <9B30768B8155174FB7C6B21ABDCD24C001DC2BEE@GAALPA1MSGUSR9N.ITServices.sbc.com>
References: <Ac0SYcs7k5DhJOMpQS+JiCq8D7XSMQ==> <9B30768B8155174FB7C6B21ABDCD24C001D687E5@GAALPA1MSGUSR9N.ITServices.sbc.com> <CABFReBqi9u914gcMsYBPTCEubv=m0KgGmdkG1j6Teco_ELSTUw@mail.gmail.com> <C0E0A32284495243BDE0AC8A066631A80D395E48@dfweml513-mbx.china.huawei.com>
In-Reply-To: <C0E0A32284495243BDE0AC8A066631A80D395E48@dfweml513-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.187.205]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <rs1983@att.com>
X-SOURCE-IP: [144.160.20.146]
X-AnalysisOut: [v=1.0 c=1 a=kIIE2rl2P-oA:10 a=xdcERly8WI4A:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:10 a=Qs8R1XBwmid1qB]
X-AnalysisOut: [FB/a8mmA==:17 a=i0EeH86SAAAA:8 a=pGLkceISAAAA:8 a=48vgC7mU]
X-AnalysisOut: [AAAA:8 a=zQP7CpKOAAAA:8 a=X5f2utlMRi2UT1uL7OUA:9 a=7-4y7_r]
X-AnalysisOut: [riAeB_9nryQ0A:7 a=wPNLvfGTeEIA:10 a=hPjdaMEvmhQA:10 a=MSl-]
X-AnalysisOut: [tDqOz04A:10 a=lZB815dzVvQA:10 a=Hz7IrDYlS0cA:10 a=i61vnaW3]
X-AnalysisOut: [fjz5gB42:21 a=Nd7fgfhQLCGCXA6B:21]
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] Interdomain/AS Multicast for CDN
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, 21 May 2012 21:34:51 -0000

Oh,  I forgot to mention.  Myself and others are putting together an outlin=
e for a draft.  We will socialize it in the next few weeks with mboned.=20


-----Original Message-----
From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]=20
Sent: Monday, May 21, 2012 5:00 PM
To: gjshep@gmail.com; SAYKO, ROBERT J
Cc: mboned@ietf.org
Subject: RE: [MBONED] Interdomain/AS Multicast for CDN

Is it related to CDNi WG as well?

Tina

> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf
> Of Greg Shepherd
> Sent: Monday, May 21, 2012 1:19 PM
> To: SAYKO, ROBERT J
> Cc: mboned@ietf.org
> Subject: Re: [MBONED] Interdomain/AS Multicast for CDN
>=20
> Inline:
>=20
> On Wed, Apr 4, 2012 at 5:52 AM, SAYKO, ROBERT J <rs1983@att.com> wrote:
> >
> > All,
> >
> >
> > As we didn't have time to complete our agenda on last Thursday I didn't
> have the opportunity to raise this topic.
> >
> > (As I am very new to IETF please excuse me if I am not following correc=
t
> protocol or process in the following)
> >
> > I would like to propose that mboned initiate work on a draft for Inter-
> domain/AS CDN Multicast. =A0I have already spoken
> > with one of our chairs, =A0Greg Shepherd, on this and he indicated that=
 he
> would support the WG taking it on.
>=20
> And I still think this is appropriate work for MBONED.
>=20
> > I am aware that CDNi is doing a lot of interdomain CDN work, =A0but the=
y
> are not addressing multicast and per their
> > chairs do not want to take on multicast at this time (or from what I
> gather in the near future). =A0 =A0I have recently
> > completed work on the ATIS interdomain MC specification and would like
> to take that work as a starting point to go
> > even further by creating a RFC through IETF.
>=20
> This seems to be the typical response in the IETF and why MBONED has
> become the mcast safety net. Additionally, this isn't protocol work so
> it fits right into our charter.
>=20
> > If mboned takes on this challenge I think our scope will be slightly
> different then if CDNi were to do it, =A0but that is fine
> > and it would not be demonstratively different I think. =A0 Since I thin=
k
> interdomain CDN MC is almost a niche I think it
> > would actually be easier to do then the caching based approach CDNi
> seems to be concentrating on.
>=20
> Agreed.
>=20
> > Interdomain CDNi is also likely to be more quickly and incorporated by
> some large operators then cache based. =A0There
> > are a number of reasons for this: =A0many operators have MC ready or
> operating backbones, =A0it is a quick starter, =A0MC
> > ready content is rapidly growing, =A0less investment then cache, =A0bes=
t
> solution for flash crowds. =A0Also, =A0large operators
> > have within their ownership several AS's with separate CDNs in some
> cases and see MC as an extremely significant
> > cost saving technology.
>=20
> From the WGs perspective, you've done the hard bit already in ATIS. We
> just need to advance this work in the IETF, possibly as a BCP draft.
>=20
> > Hopefully, =A0the WG will favorably consider taking this on. =A0I would=
 be
> happy to be lead author, =A0but would of course like
> > as much help as possible. =A0Please give me your comments and questions=
.
>=20
> Again, I'm all for it. Anyone on the list interested in helping Bob
> author the draft?
>=20
> Thanks!,
> Greg
>=20
> > Regards,
> > Bob Sayko
> >
> >
> > _______________________________________________
> > 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 May 22 14:17: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 E622021F85A5 for <mboned@ietfa.amsl.com>; Tue, 22 May 2012 14:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150,  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 kerQGXdJm8i3 for <mboned@ietfa.amsl.com>; Tue, 22 May 2012 14:17:30 -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 CF4AC21F8598 for <mboned@ietf.org>; Tue, 22 May 2012 14:17:29 -0700 (PDT)
Received: by yenq13 with SMTP id q13so6878430yen.31 for <mboned@ietf.org>; Tue, 22 May 2012 14:17:29 -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=GCwRo9lMs6aOVWGU5GlCsj1knSXDg6ya1fMim5+Ejos=; b=y0pPIHYEXk3n6Nl6wAz0aAbuP1eeIP3T/LzvE9I/Rr7IpqeY4drVJclVURCfXh+W2C +z7alLVtftYj5KJto7dZ5V9RuBhrGA9I6wFT0R3He0UyuZN/do+e9MrkX7i3jr/CuW2t kMwG0+BSddzsXG0x6ZFvwyvDeNqjbTeOjrGHP8arAhC8xVParNHWHqzcXat32YbJJ7rU ed/OXreISK9yHTlPGe7BBImG07kA1SkgqzDjfRSe/X3bqNfgtrouqwfzqfPs/U6Fj9Q3 bXT3l78c2dlMu6Q4XrE5oRz71uWOQgoBNo1ahjjc5f6kS5PmvASLPmWQexIg9dvK2Sg/ cPVw==
MIME-Version: 1.0
Received: by 10.50.179.38 with SMTP id dd6mr11182563igc.9.1337721448498; Tue, 22 May 2012 14:17:28 -0700 (PDT)
Received: by 10.231.78.10 with HTTP; Tue, 22 May 2012 14:17:28 -0700 (PDT)
In-Reply-To: <CABFReBof8GKz=yzmPxLGk+eTsUE20PYvZOyO9fqMcY8oFcwnow@mail.gmail.com>
References: <CABFReBqo43QsBWwu=_nbDgw-eoK1S2+8xszTXY1Zm=KLhmvRPA@mail.gmail.com> <CABFReBof8GKz=yzmPxLGk+eTsUE20PYvZOyO9fqMcY8oFcwnow@mail.gmail.com>
Date: Tue, 22 May 2012 16:17:28 -0500
Message-ID: <CAC8QAcddm=y=Tk3X3zbVQbG397ck2sep03ab4c07q0itpxRw7A@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: gjshep@gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: mboned@ietf.org
Subject: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
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, 22 May 2012 21:17:31 -0000

I support the call.

Behcet

On Mon, May 21, 2012 at 2:30 PM, Greg Shepherd <gjshep@gmail.com> wrote:
> We're half way through the 3 week WGLC for AMT and we've received no
> responses. Please read and respond ASAP so we can progress.
>
> Thanks,
> Greg
>
> On Thu, May 10, 2012 at 10:33 AM, Greg Shepherd <gjshep@gmail.com> wrote:
>> *,
>>
>> Yes, I think we may finally be here! The Paris and post-Paris
>> discussions were addressed in the finally rev so it is now time for
>> WGLC for draft-ietf-mboned-auto-multicast-13:
>>
>> https://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast/
>>
>> It is quite long so we'll give it three weeks for responses before
>> moving it along. Please respond by May 31st. And as always, we need
>> votes of approval as much as comments and issues. Let's see this
>> finally move to req pub!
>>
>> Thanks to everyone who has been involved throughout the past +decade. :p
>>
>> MBONED Chairs
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned

From internet-drafts@ietf.org  Wed May 23 05:50:55 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 244B221F872A; Wed, 23 May 2012 05:50:55 -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 Uo1wtgs9rr3E; Wed, 23 May 2012 05:50:54 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 095CA21F871D; Wed, 23 May 2012 05:50:54 -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.02
Message-ID: <20120523125054.30986.46971.idtracker@ietfa.amsl.com>
Date: Wed, 23 May 2012 05:50:54 -0700
Cc: mboned@ietf.org
Subject: [MBONED] I-D Action: draft-ietf-mboned-64-multicast-address-format-02.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, 23 May 2012 12:50:55 -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=
 IETF.

	Title           : IPv6 Multicast Address Format With Embedded IPv4 Multica=
st Address
	Author(s)       : Mohamed Boucadair
                          Jacni Qin
                          Yiu L. Lee
                          Stig Venaas
                          Xing Li
                          Mingwei Xu
	Filename        : draft-ietf-mboned-64-multicast-address-format-02.txt
	Pages           : 15
	Date            : 2012-05-23

   This document specifies an extension to the IPv6 multicast addressing
   architecture to be used in the context of IPv4-IPv6 interconnection.
   In particular, this document defines an address format for IPv4-
   embedded IPv6 multicast addresses.  This address format can be used
   for IPv4-IPv6 translation or encapsulation schemes.

   This document updates RFC4291.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mboned-64-multicast-address-=
format-02.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mboned-64-multicast-address-f=
ormat-02.txt

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


From mohamed.boucadair@orange.com  Wed May 23 06:03:34 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 079AF21F8751 for <mboned@ietfa.amsl.com>; Wed, 23 May 2012 06:03:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[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 ROI7Zp+Ia57n for <mboned@ietfa.amsl.com>; Wed, 23 May 2012 06:03:33 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 5B11921F874F for <mboned@ietf.org>; Wed, 23 May 2012 06:03:28 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 146CA18C2B4 for <mboned@ietf.org>; Wed, 23 May 2012 15:03:27 +0200 (CEST)
Received: from PUEXCH71.nanterre.francetelecom.fr (unknown [10.101.44.33]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id EB0E6238055 for <mboned@ietf.org>; Wed, 23 May 2012 15:03:26 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH71.nanterre.francetelecom.fr ([10.101.44.33]) with mapi; Wed, 23 May 2012 15:03:26 +0200
From: <mohamed.boucadair@orange.com>
To: "mboned@ietf.org" <mboned@ietf.org>
Date: Wed, 23 May 2012 15:03:25 +0200
Thread-Topic: I-D Action: draft-ietf-mboned-64-multicast-address-format-02.txt
Thread-Index: Ac044r1XXD1MS9TfRZWQ3Md+O3DAXgAABQgw
Message-ID: <94C682931C08B048B7A8645303FDC9F36E2B9B547E@PUEXCB1B.nanterre.francetelecom.fr>
References: <20120523125054.30986.46971.idtracker@ietfa.amsl.com>
In-Reply-To: <20120523125054.30986.46971.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="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.5.23.113319
Subject: Re: [MBONED] I-D Action: draft-ietf-mboned-64-multicast-address-format-02.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, 23 May 2012 13:03:34 -0000

Dear all,

An updated version taking into account the comments received during the IET=
F LC has been submitted:

* Editorial changes as suggested in SM's review
* Title change (comment from C. Bormann)
* Added a new section to describe the algorithm to embed/extract the IPv4 a=
ddress (comment from C. Bormann)
* Added some pointers to documents making use of the address format (commen=
t from C. Bormann)
* Added an appendix to explain why an M-bit is needed (comment from C. Borm=
ann)
* Added an appendix to explain why an address format is needed  (comment fr=
om C. Bormann)
* Added examples of means to provision the MPREFIX64  (comment from C. Borm=
ann)
=20
Diff from previous version:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-mboned-64-multicast-address=
-format-02

Cheers,
Med

>-----Message d'origine-----
>De : i-d-announce-bounces@ietf.org=20
>[mailto:i-d-announce-bounces@ietf.org] De la part de=20
>internet-drafts@ietf.org
>Envoy=E9 : mercredi 23 mai 2012 14:51
>=C0 : i-d-announce@ietf.org
>Cc : mboned@ietf.org
>Objet : I-D Action:=20
>draft-ietf-mboned-64-multicast-address-format-02.txt
>
>
>A New Internet-Draft is available from the on-line=20
>Internet-Drafts directories. This draft is a work item of the=20
>MBONE Deployment Working Group of the IETF.
>
>	Title           : IPv6 Multicast Address Format 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-02.txt
>	Pages           : 15
>	Date            : 2012-05-23
>
>   This document specifies an extension to the IPv6 multicast=20
>addressing
>   architecture to be used in the context of IPv4-IPv6 interconnection.
>   In particular, this document defines an address format for IPv4-
>   embedded IPv6 multicast addresses.  This address format can be used
>   for IPv4-IPv6 translation or encapsulation schemes.
>
>   This document updates RFC4291.
>
>
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-mboned-64-multic
>ast-address-format-02.txt
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>This Internet-Draft can be retrieved at:
>ftp://ftp.ietf.org/internet-drafts/draft-ietf-mboned-64-multica
>st-address-format-02.txt
>
>The IETF datatracker page for this Internet-Draft is:
>https://datatracker.ietf.org/doc/draft-ietf-mboned-64-multicast
>-address-format/
>
>_______________________________________________
>I-D-Announce mailing list
>I-D-Announce@ietf.org
>https://www.ietf.org/mailman/listinfo/i-d-announce
>Internet-Draft directories: http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=

From rbonica@juniper.net  Wed May 23 06:09:36 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 DE43521F875C for <mboned@ietfa.amsl.com>; Wed, 23 May 2012 06:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.499
X-Spam-Level: 
X-Spam-Status: No, score=-106.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 zkPlz233dH-k for <mboned@ietfa.amsl.com>; Wed, 23 May 2012 06:09:36 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id 3EB6721F875B for <mboned@ietf.org>; Wed, 23 May 2012 06:09:36 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKT7zhj1BpXYE2w0mhWsVvN2+3JGOWfRNF@postini.com; Wed, 23 May 2012 06:09:36 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 23 May 2012 06:09:10 -0700
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by p-cldfe01-hq.jnpr.net (172.24.192.59) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 23 May 2012 06:09:10 -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, 23 May 2012 09:09:09 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "mboned@ietf.org" <mboned@ietf.org>
Date: Wed, 23 May 2012 09:09:08 -0400
Thread-Topic: [MBONED] I-D Action: draft-ietf-mboned-64-multicast-address-format-02.txt
Thread-Index: Ac045HkKxuOSOPwVQJW4WyOEfL7CbQAADXvw
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76C03F330@EMBX01-WF.jnpr.net>
References: <mailman.1297.1337778214.3389.mboned@ietf.org>
In-Reply-To: <mailman.1297.1337778214.3389.mboned@ietf.org>
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: Re: [MBONED] I-D Action: draft-ietf-mboned-64-multicast-address-format-02.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, 23 May 2012 13:09:37 -0000

Hi Med,

Thanks for posting this draft. Do you think that this draft version address=
es all of the comments from 6man? If so, you might want to post a similar m=
essage to the 6man mailing list.=20

                                          Ron


> Date: Wed, 23 May 2012 15:03:25 +0200
> From: <mohamed.boucadair@orange.com>
> To: "mboned@ietf.org" <mboned@ietf.org>
> Subject: Re: [MBONED] I-D Action:
> 	draft-ietf-mboned-64-multicast-address-format-02.txt
> Message-ID:
> 	<94C682931C08B048B7A8645303FDC9F36E2B9B547E@PUEXCB1B.nanterre.fra
> ncetelecom.fr>
>=20
> Content-Type: text/plain; charset=3D"iso-8859-1"
>=20
> Dear all,
>=20
> An updated version taking into account the comments received during the
> IETF LC has been submitted:
>=20
> * Editorial changes as suggested in SM's review
> * Title change (comment from C. Bormann)
> * Added a new section to describe the algorithm to embed/extract the
> IPv4 address (comment from C. Bormann)
> * Added some pointers to documents making use of the address format
> (comment from C. Bormann)
> * Added an appendix to explain why an M-bit is needed (comment from C.
> Bormann)
> * Added an appendix to explain why an address format is needed
> (comment from C. Bormann)
> * Added examples of means to provision the MPREFIX64  (comment from C.
> Bormann)
>=20
> Diff from previous version:
> http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-mboned-64-multicast-
> address-format-02
>=20
> Cheers,
> Med
>=20


From mohamed.boucadair@orange.com  Wed May 23 06:15:22 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 DDA9621F853C for <mboned@ietfa.amsl.com>; Wed, 23 May 2012 06:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[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 2orMh-t9f+8k for <mboned@ietfa.amsl.com>; Wed, 23 May 2012 06:15:22 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id ED85E21F84FF for <mboned@ietf.org>; Wed, 23 May 2012 06:15:21 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 623FE32464E; Wed, 23 May 2012 15:15:21 +0200 (CEST)
Received: from puexch91.nanterre.francetelecom.fr (unknown [10.101.44.48]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 4982123804B; Wed, 23 May 2012 15:15:21 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by puexch91.nanterre.francetelecom.fr ([10.101.44.48]) with mapi; Wed, 23 May 2012 15:15:21 +0200
From: <mohamed.boucadair@orange.com>
To: Ronald Bonica <rbonica@juniper.net>, "mboned@ietf.org" <mboned@ietf.org>
Date: Wed, 23 May 2012 15:15:20 +0200
Thread-Topic: [MBONED] I-D Action: draft-ietf-mboned-64-multicast-address-format-02.txt
Thread-Index: Ac045HkKxuOSOPwVQJW4WyOEfL7CbQAADXvwAAAtquA=
Message-ID: <94C682931C08B048B7A8645303FDC9F36E2B9B5489@PUEXCB1B.nanterre.francetelecom.fr>
References: <mailman.1297.1337778214.3389.mboned@ietf.org> <13205C286662DE4387D9AF3AC30EF456D76C03F330@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D76C03F330@EMBX01-WF.jnpr.net>
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.5.23.113319
Subject: Re: [MBONED] I-D Action: draft-ietf-mboned-64-multicast-address-format-02.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, 23 May 2012 13:15:23 -0000

Dear Ron,

My read of the messages exchanged in 6man (archives available here http://w=
ww.ietf.org/mail-archive/web/ipv6/current/msg15857.html) is there is no str=
ong opinion to abandon the current design in favour of using the remaining =
flag.=20

I can sent an e-mail to 6man if you suggest so.

Cheers,
Med

>-----Message d'origine-----
>De : mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org]=20
>De la part de Ronald Bonica
>Envoy=E9 : mercredi 23 mai 2012 15:09
>=C0 : mboned@ietf.org
>Objet : Re: [MBONED] I-D Action:=20
>draft-ietf-mboned-64-multicast-address-format-02.txt
>
>Hi Med,
>
>Thanks for posting this draft. Do you think that this draft=20
>version addresses all of the comments from 6man? If so, you=20
>might want to post a similar message to the 6man mailing list.=20
>
>                                          Ron
>
>
>> Date: Wed, 23 May 2012 15:03:25 +0200
>> From: <mohamed.boucadair@orange.com>
>> To: "mboned@ietf.org" <mboned@ietf.org>
>> Subject: Re: [MBONED] I-D Action:
>> 	draft-ietf-mboned-64-multicast-address-format-02.txt
>> Message-ID:
>> =09
><94C682931C08B048B7A8645303FDC9F36E2B9B547E@PUEXCB1B.nanterre.fra
>> ncetelecom.fr>
>>=20
>> Content-Type: text/plain; charset=3D"iso-8859-1"
>>=20
>> Dear all,
>>=20
>> An updated version taking into account the comments received=20
>during the
>> IETF LC has been submitted:
>>=20
>> * Editorial changes as suggested in SM's review
>> * Title change (comment from C. Bormann)
>> * Added a new section to describe the algorithm to embed/extract the
>> IPv4 address (comment from C. Bormann)
>> * Added some pointers to documents making use of the address format
>> (comment from C. Bormann)
>> * Added an appendix to explain why an M-bit is needed=20
>(comment from C.
>> Bormann)
>> * Added an appendix to explain why an address format is needed
>> (comment from C. Bormann)
>> * Added examples of means to provision the MPREFIX64 =20
>(comment from C.
>> Bormann)
>>=20
>> Diff from previous version:
>> http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-mboned-64-multicast-
>> address-format-02
>>=20
>> Cheers,
>> Med
>>=20
>
>_______________________________________________
>MBONED mailing list
>MBONED@ietf.org
>https://www.ietf.org/mailman/listinfo/mboned
>=

From rbonica@juniper.net  Wed May 23 06:20:17 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 EC80021F8499 for <mboned@ietfa.amsl.com>; Wed, 23 May 2012 06:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.524
X-Spam-Level: 
X-Spam-Status: No, score=-106.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 Zq5NMfO3wI7S for <mboned@ietfa.amsl.com>; Wed, 23 May 2012 06:20:16 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id 26D8621F8497 for <mboned@ietf.org>; Wed, 23 May 2012 06:20:13 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKT7zkDChIUFwhTKmA1cbeYK4oSogtllTe@postini.com; Wed, 23 May 2012 06:20:15 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 23 May 2012 06:18:39 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Wed, 23 May 2012 09:18:38 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "mboned@ietf.org" <mboned@ietf.org>
Date: Wed, 23 May 2012 09:18:37 -0400
Thread-Topic: [MBONED] I-D Action: draft-ietf-mboned-64-multicast-address-format-02.txt
Thread-Index: Ac045HkKxuOSOPwVQJW4WyOEfL7CbQAADXvwAAAtquAAAEaNMA==
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76C03F356@EMBX01-WF.jnpr.net>
References: <mailman.1297.1337778214.3389.mboned@ietf.org> <13205C286662DE4387D9AF3AC30EF456D76C03F330@EMBX01-WF.jnpr.net> <94C682931C08B048B7A8645303FDC9F36E2B9B5489@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E2B9B5489@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [MBONED] I-D Action: draft-ietf-mboned-64-multicast-address-format-02.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, 23 May 2012 13:20:17 -0000

Please do.

          Ron


> -----Original Message-----
> From: mohamed.boucadair@orange.com
> [mailto:mohamed.boucadair@orange.com]
> Sent: Wednesday, May 23, 2012 9:15 AM
> To: Ronald Bonica; mboned@ietf.org
> Subject: RE: [MBONED] I-D Action: draft-ietf-mboned-64-multicast-
> address-format-02.txt
>=20
> Dear Ron,
>=20
> My read of the messages exchanged in 6man (archives available here
> http://www.ietf.org/mail-archive/web/ipv6/current/msg15857.html) is
> there is no strong opinion to abandon the current design in favour of
> using the remaining flag.
>=20
> I can sent an e-mail to 6man if you suggest so.
>=20
> Cheers,
> Med
>=20
> >-----Message d'origine-----
> >De : mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] De la
> >part de Ronald Bonica Envoy=E9 : mercredi 23 mai 2012 15:09 =C0 :
> >mboned@ietf.org Objet : Re: [MBONED] I-D Action:
> >draft-ietf-mboned-64-multicast-address-format-02.txt
> >
> >Hi Med,
> >
> >Thanks for posting this draft. Do you think that this draft version
> >addresses all of the comments from 6man? If so, you might want to post
> >a similar message to the 6man mailing list.
> >
> >                                          Ron
> >
> >
> >> Date: Wed, 23 May 2012 15:03:25 +0200
> >> From: <mohamed.boucadair@orange.com>
> >> To: "mboned@ietf.org" <mboned@ietf.org>
> >> Subject: Re: [MBONED] I-D Action:
> >> 	draft-ietf-mboned-64-multicast-address-format-02.txt
> >> Message-ID:
> >>
> ><94C682931C08B048B7A8645303FDC9F36E2B9B547E@PUEXCB1B.nanterre.fra
> >> ncetelecom.fr>
> >>
> >> Content-Type: text/plain; charset=3D"iso-8859-1"
> >>
> >> Dear all,
> >>
> >> An updated version taking into account the comments received
> >during the
> >> IETF LC has been submitted:
> >>
> >> * Editorial changes as suggested in SM's review
> >> * Title change (comment from C. Bormann)
> >> * Added a new section to describe the algorithm to embed/extract the
> >> IPv4 address (comment from C. Bormann)
> >> * Added some pointers to documents making use of the address format
> >> (comment from C. Bormann)
> >> * Added an appendix to explain why an M-bit is needed
> >(comment from C.
> >> Bormann)
> >> * Added an appendix to explain why an address format is needed
> >> (comment from C. Bormann)
> >> * Added examples of means to provision the MPREFIX64
> >(comment from C.
> >> Bormann)
> >>
> >> Diff from previous version:
> >> http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-mboned-64-multicast-
> >> address-format-02
> >>
> >> Cheers,
> >> Med
> >>
> >
> >_______________________________________________
> >MBONED mailing list
> >MBONED@ietf.org
> >https://www.ietf.org/mailman/listinfo/mboned
> >

From marshall.eubanks@gmail.com  Thu May 24 03:27:12 2012
Return-Path: <marshall.eubanks@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 4CA2F21F8623 for <mboned@ietfa.amsl.com>; Thu, 24 May 2012 03:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.171
X-Spam-Level: 
X-Spam-Status: No, score=-103.171 tagged_above=-999 required=5 tests=[AWL=-0.371, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799, 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 ABlNdyMuC+Ph for <mboned@ietfa.amsl.com>; Thu, 24 May 2012 03:27:11 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5FE4521F84C3 for <mboned@ietf.org>; Thu, 24 May 2012 03:27:11 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so6719360lbb.31 for <mboned@ietf.org>; Thu, 24 May 2012 03:27:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=LLN7fx+bFKePjTPIPcJYzF7isGcj2gmmbe1Rc5eYg2I=; b=kk0e0mRt9ZIpmPQujmAyNgQTzZXgzEokt2PP9CX0Khm9OcgAKvI1j4Ej9YNWBZcNdO ohINSb1gxNq4tcGhu6PrDMFsCtk8JoAQ+T2GHrYHdLsg3PueUUolRD3e3C29jqaoIKm2 tiY79UOAyUgaYVWqp/BvGoK+pc4g28vDgl8/WG/uUi6rGg/S7q0UbLwAq/F+m/ZeOnGv MC91i6MRGAasspl/DUlqpvav9L50QlOJaxXpfc5x4YojkxYgrnCW2W2TLcuWTpmB0y5W ITLQPttzBHsDvBd9mY7B79nA1w5CrhLsFXW8Eyuc0mT4j6P/tGjSqC96qtrG1C8q+xfw 8cPQ==
MIME-Version: 1.0
Received: by 10.112.28.226 with SMTP id e2mr12168253lbh.96.1337855230311; Thu, 24 May 2012 03:27:10 -0700 (PDT)
Received: by 10.112.132.65 with HTTP; Thu, 24 May 2012 03:27:10 -0700 (PDT)
In-Reply-To: <02be01cd390c$2d43a0d0$87cae270$@iab.org>
References: <02be01cd390c$2d43a0d0$87cae270$@iab.org>
Date: Thu, 24 May 2012 06:27:10 -0400
Message-ID: <CAJNg7V+i--LHA4ync2+LONqkSr+uLdQOvF5-dx09jFCYu9X0Zw@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: mboned@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [MBONED] Fwd: Call for Papers: IAB/IRTF Workshop on Congestion Control for Interactive Real-Time Communication, July 28, 2012 Vancouver, Canada
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, 24 May 2012 10:27:12 -0000

FYI, in case you don't get IETF announce.

Regards
Marshall


---------- Forwarded message ----------
From: IAB Chair <iab-chair@iab.org>
Date: Wed, May 23, 2012 at 1:47 PM
Subject: Call for Papers: IAB/IRTF Workshop on Congestion Control for
Interactive Real-Time Communication, July 28, 2012 Vancouver, Canada
To: ietf-announce@ietf.org
Cc: iab@iab.org


IAB / IRTF Workshop on
Congestion Control for Interactive
Real-Time Communication

July 28, 2012
Vancouver, Canada



The IAB and IRTF will hold a workshop on Congestion Control for
Interactive Real-Time Communication" in Vancouver, Canada on Saturday,
July 28th, 2012 prior to the IETF-84 meeting (see
http://www.ietf.org/meeting/84/index.html). =A0Participation at the
workshop is free of charge. There is no requirement to either register
with or attend the IETF-84 meeting that follows the workshop.



The workshop organizers would like to foster a discussion on:

What are appropriate congestion signals to use for interactive media and da=
ta?
What existing congestion control algorithms are appropriate for
interactive media and data? What properties would be desirable in new
congestion control algorithms?
Measurement and/or simulations of new congestion signals (e.g.,
delay-based) and their interaction with existing congestion control
mechanisms.
What are good available techniques for adjusting sending rates for
interactive media and data? What are the limits of those techniques?
What properties would be desirable in new techniques?
What application-specific considerations have to be taken into account?
How can we ensure that real-time communications are well-behaved with
respect to other Internet applications while still providing good
quality?
What should the IETF and/or IRTF do?

The organizers seek position papers on any or all of these topics, as
well as other topics related to congestion control for interactive
realtime media.



Every prospective workshop participant must submit a position paper
containing a name and an email address. Authors of accepted papers
will be invited to the workshop. Papers up to 3 pages, formatted in
HTML, PDF, or plain text (for example, as a submitted Internet-Draft)
are ideal. Accepted position papers will be published.=A0 Additional
details about the meeting venue will be provided to authors of
accepted papers.

Important Dates

Position paper submission deadline: =A0=A0=A0=A0=A0=A0=A0=A0 June 23, 2012
Notification to paper authors: =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0 June 30, 2012
Workshop date: =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 July =
28, 2012

Additional Details

Additional details on the workshop as well as the submission process
is available at http://www.iab.org/cc-workshop/

Contact

To sponsors: If you are interested to help us working towards better
interactive media congestion control mechanisms on the Internet (such
as by making a contribution towards catering costs and room rental),
please contact us!

In case of questions please send email to mary.ietf.barnes at gmail.com.

From Tina.Tsou.Zouting@huawei.com  Thu May 24 09:03:38 2012
Return-Path: <Tina.Tsou.Zouting@huawei.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 4795721F853C for <mboned@ietfa.amsl.com>; Thu, 24 May 2012 09:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.198
X-Spam-Level: 
X-Spam-Status: No, score=-6.198 tagged_above=-999 required=5 tests=[AWL=0.400,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 X20sMKjohZfX for <mboned@ietfa.amsl.com>; Thu, 24 May 2012 09:03:37 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2698121F85F0 for <mboned@ietf.org>; Thu, 24 May 2012 09:03:37 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AGM60895; Thu, 24 May 2012 12:03:36 -0400 (EDT)
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 24 May 2012 09:01:46 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.80]) by dfweml408-hub.china.huawei.com ([10.193.5.134]) with mapi id 14.01.0323.003; Thu, 24 May 2012 09:01:48 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Thread-Topic: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
Thread-Index: Ac0olW4tpAJfzZWwTw2lKRKI4vlTgAGPwEowAOi2jQAAKqIPgAGpLR8W
Date: Thu, 24 May 2012 16:01:48 +0000
Message-ID: <B641703E-A8F1-4B12-9679-4D72F81C6A45@huawei.com>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com> <4FB1B592.1090706@jacni.com>, <B0147C3DD45E42478038FC347CCB65FE02BB90F50B@XCH-MW-08V.mw.nos.boeing.com>
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE02BB90F50B@XCH-MW-08V.mw.nos.boeing.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_B641703EA8F14B1296794D72F81C6A45huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 24 May 2012 16:03:38 -0000

--_000_B641703EA8F14B1296794D72F81C6A45huaweicom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Bert,
Thank you for your support.

What you are saying suggests that it is only the third part of the existing=
 document that makes real sense to an operator considering the problem of a=
ddress acquisition. Maybe the document has to be organized differently. Ins=
tead of looking at theoretical approaches to the problem, maybe it should l=
ook at what might work for specific operator scenarios. We could think abou=
t what are the relevant variables to describe these scenarios. Whether the =
source and receiver support the same IP version is obviously one aspect, an=
d whether the source is under the control of the provider (so that the prov=
ider can control address mapping.) Then there are the variations in archite=
cture for creation and provision of the EPG.

Does this seem to be on the right track?

Tina

On May 15, 2012, at 3:07 PM, "Manfredi, Albert E" <albert.e.manfredi@boeing=
.com<mailto:albert.e.manfredi@boeing.com>> wrote:

Tina et al,

I also support this effort. A couple of comments:

My reaction to the Reactive Strategy in 3.1 was that it=92s too hard. Inste=
ad of making the IPv4 receiver kludge up IPv6 addresses, presumably kludge =
up MLD(?), and then convert IPv6 multicasts, why not just install an IPv6 s=
tack in that receiver? (And yet, the counter to this is that Microsoft Offi=
ce 2003 is capable of ingesting Office 2007 files quite well, and maybe eve=
n Office 2010 files, and all done in the =93receiver.=94 Still, Office suit=
es are expensive for users, whereas IP stacks are not.)

The Dynamic Modification in 3.2, by the network, seems to be a more realist=
ic option.

The Administrative Preparation in 3.3 seems to be an elaboration of 3.2. It=
 merely adds a description of mechanisms that may be used to obtain info on=
 the receiver, where 3.2 only said:

   It requires that an element in that network must
   intercept program guide information destined to the receiver, locate
   the access information, and map IP addresses to an alternate version
   as necessary to suit the receiver.

Isn=92t 3.3 describing HOW the network knows to =93suit the receiver=94?

Another option would be for the network to transfer both multicasts, and si=
mply respond according to whether the receiver used IGMP or MLD to join the=
 multicast. And the receiver would know the appropriate IPv4 or IPv6 multic=
ast group (and potentially source IP) using OOB means, like the EPG itself,=
 or the EPG plus an associated SIP session, or EPG plus SDP. (Wasn=92t ther=
e a discussion some time ago about =93why use SDP anymore?=94) Assuming ban=
dwidth isn=92t in very short supply, my own approach would be either to get=
 both versions from the source, or to create the other version at the initi=
al ingress point to my network.

Bert


From: mboned-bounces@ietf.org<mailto:mboned-bounces@ietf.org> [mailto:mbone=
d-bounces@ietf.org] On Behalf Of Jacni Qin
Sent: Monday, May 14, 2012 9:47 PM
To: Tina TSOU
Cc: 'mboned@ietf.org<mailto:mboned@ietf.org>'
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01

Hi authors,

Some questions about the "possible solutions" proposed,

3.1, as stated by itself, probably not reasonable from implementation stand=
point.

For 3.2 and the first approach in 3.3, I guess they're ALGs, and IMHO, the =
discussions in Section 4.1 of the http://tools.ietf.org/html/draft-ietf-mbo=
ned-v4v6-mcast-ps-00, are sufficient.

About the second approach in 3.3, not sure I fully understand it yet, but s=
o far I see it also a kind of ALG.


Cheers,
Jacni

On 5/11/2012 Friday 1:49 AM, Tina TSOU wrote:
Dear chairs,
Would you ask the WG for adoption of draft-tsou-mboned-multrans-addr-acquis=
ition-01 as WG document?

Thank you and have a good day.

Tina and co-authors

From: Tina TSOU
Sent: Wednesday, May 02, 2012 11:58 AM
To: mboned@ietf.org<mailto:mboned@ietf.org>
Subject: draft-tsou-mboned-multrans-addr-acquisition-01


Now that the multicast transition framework document is officially accepted=
, is the Working Group prepared also to take on the topic of address acquis=
ition, which is one of the tasks it identifies?
If so, would draft-tsou-mboned-multrans-addr-acquisition-01 be acceptable a=
s a starting point?

Tina





_______________________________________________

MBONED mailing list

MBONED@ietf.org<mailto:MBONED@ietf.org>

https://www.ietf.org/mailman/listinfo/mboned

--_000_B641703EA8F14B1296794D72F81C6A45huaweicom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body bgcolor=3D"#FFFFFF">
<div>Bert,&nbsp;</div>
<div>Thank you for your support.</div>
<div><br>
</div>
<div>What you are saying suggests that it is only the third part of the exi=
sting document that makes real sense to an operator considering the problem=
 of address acquisition. Maybe the document has to be organized differently=
. Instead of looking at theoretical
 approaches to the problem, maybe it should look at what might work for spe=
cific operator scenarios. We could think about what are the relevant variab=
les to describe these scenarios. Whether the source and receiver support th=
e same IP version is obviously one
 aspect, and whether the source is under the control of the provider (so th=
at the provider can control address mapping.) Then there are the variations=
 in architecture for creation and provision of the EPG.<br>
<span></span><br>
Does this seem to be on the right track?<br>
<br>
Tina</div>
<div><br>
On May 15, 2012, at 3:07 PM, &quot;Manfredi, Albert E&quot; &lt;<a href=3D"=
mailto:albert.e.manfredi@boeing.com">albert.e.manfredi@boeing.com</a>&gt; w=
rote:<br>
<br>
</div>
<div></div>
<blockquote type=3D"cite">
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Times New Roman","serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">Tina et al,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">I also support this effor=
t. A couple of comments:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">My reaction to the Reacti=
ve Strategy in 3.1 was that it=92s too hard. Instead of making the IPv4 rec=
eiver kludge up IPv6 addresses, presumably kludge up MLD(?),
 and then convert IPv6 multicasts, why not just install an IPv6 stack in th=
at receiver? (And yet, the counter to this is that Microsoft Office 2003 is=
 capable of ingesting Office 2007 files quite well, and maybe even Office 2=
010 files, and all done in the =93receiver.=94
 Still, Office suites are expensive for users, whereas IP stacks are not.)<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">The Dynamic Modification =
in 3.2, by the network, seems to be a more realistic option.<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">The Administrative Prepar=
ation in 3.3 seems to be an elaboration of 3.2. It merely adds a descriptio=
n of mechanisms that may be used to obtain info on the receiver,
 where 3.2 only said:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:windowtext">&nbsp;&nbsp;=
 It requires that an element in that network must<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:windowtext">&nbsp;&nbsp;=
 intercept program guide information destined to the receiver, locate<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:windowtext">&nbsp;&nbsp;=
 the access information, and map IP addresses to an alternate version<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:windowtext">&nbsp;&nbsp; as necessary to suit the rec=
eiver.</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Ro=
man&quot;,&quot;serif&quot;;color:blue">
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">Isn=92t 3.3 describing HO=
W the network knows to =93suit the receiver=94?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">Another option would be f=
or the network to transfer both multicasts, and simply respond according to=
 whether the receiver used IGMP or MLD to join the multicast.
 And the receiver would know the appropriate IPv4 or IPv6 multicast group (=
and potentially source IP) using OOB means, like the EPG itself, or the EPG=
 plus an associated SIP session, or EPG plus SDP. (Wasn=92t there a discuss=
ion some time ago about =93why use SDP
 anymore?=94) Assuming bandwidth isn=92t in very short supply, my own appro=
ach would be either to get both versions from the source, or to create the =
other version at the initial ingress point to my network.<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">Bert<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext">
<a href=3D"mailto:mboned-bounces@ietf.org">mboned-bounces@ietf.org</a> [mai=
lto:mboned-bounces@ietf.org]
<b>On Behalf Of </b>Jacni Qin<br>
<b>Sent:</b> Monday, May 14, 2012 9:47 PM<br>
<b>To:</b> Tina TSOU<br>
<b>Cc:</b> '<a href=3D"mailto:mboned@ietf.org">mboned@ietf.org</a>'<br>
<b>Subject:</b> Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01=
<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi authors,<br>
<br>
Some questions about the &quot;possible solutions&quot; proposed,<br>
<br>
3.1, as stated by itself, probably not reasonable from implementation stand=
point.<br>
<br>
For 3.2 and the first approach in 3.3, I guess they're ALGs, and IMHO, the =
discussions in Section 4.1 of the
<a href=3D"http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00">h=
ttp://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00</a>, are suffi=
cient.<br>
<br>
About the second approach in 3.3, not sure I fully understand it yet, but s=
o far I see it also a kind of ALG.<br>
<br>
<br>
Cheers,<br>
Jacni<br>
<br>
On 5/11/2012 Friday 1:49 AM, Tina TSOU wrote: <o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Dear chairs,</span><o:=
p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Would you ask the WG f=
or adoption of draft-tsou-mboned-multrans-addr-acquisition-01 as WG documen=
t?</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thank you and have a g=
ood day.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Tina and co-authors</s=
pan><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Tina TSO=
U
<br>
<b>Sent:</b> Wednesday, May 02, 2012 11:58 AM<br>
<b>To:</b> <a href=3D"mailto:mboned@ietf.org">mboned@ietf.org</a><br>
<b>Subject:</b> draft-tsou-mboned-multrans-addr-acquisition-01</span><o:p><=
/o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">Now that the multicast transition framework docum=
ent is officially accepted, is the Working Group prepared also to take on t=
he topic of address acquisition, which is one of the tasks it identifies?<o=
:p></o:p></p>
<p class=3D"MsoNormal">If so, would draft-tsou-mboned-multrans-addr-acquisi=
tion-01 be acceptable as a starting point?<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Tina<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>MBONED mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:MBONED@ietf.org">MBONED@ietf.org</a><o:p></o:p></pre=
>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/mboned">https://www.i=
etf.org/mailman/listinfo/mboned</a><o:p></o:p></pre>
</div>
</div>
</blockquote>
</body>
</html>

--_000_B641703EA8F14B1296794D72F81C6A45huaweicom_--

From albert.e.manfredi@boeing.com  Thu May 24 13:02:10 2012
Return-Path: <albert.e.manfredi@boeing.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 B934511E8086 for <mboned@ietfa.amsl.com>; Thu, 24 May 2012 13:02:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 nGzQU1zyIXsc for <mboned@ietfa.amsl.com>; Thu, 24 May 2012 13:02:07 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id 4095211E80D5 for <mboned@ietf.org>; Thu, 24 May 2012 13:02:07 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id q4OK26YT020974 for <mboned@ietf.org>; Thu, 24 May 2012 15:02:06 -0500
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.16.37]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id q4OK25sE020959 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 24 May 2012 15:02:05 -0500
Received: from blv-av-01.boeing.com (localhost.localdomain [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id q4OK243x006672; Thu, 24 May 2012 13:02:04 -0700
Received: from XCH-MWHT-01.mw.nos.boeing.com (xch-mwht-01.mw.nos.boeing.com [134.57.113.35]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q4OK23rY006625 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 24 May 2012 13:02:04 -0700
Received: from XCH-MWPFX-01.mw.nos.boeing.com (132.173.24.10) by XCH-MWHT-01.mw.nos.boeing.com (134.57.113.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 24 May 2012 15:02:03 -0500
Received: from XCH-MW-08V.mw.nos.boeing.com ([134.57.118.180]) by XCH-MWPFX-01.mw.nos.boeing.com ([132.173.24.10]) with mapi; Thu, 24 May 2012 15:02:02 -0500
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Date: Thu, 24 May 2012 15:02:00 -0500
Thread-Topic: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
Thread-Index: Ac0olW4tpAJfzZWwTw2lKRKI4vlTgAGPwEowAOi2jQAAKqIPgAGpLR8WAAgXMTA=
Message-ID: <B0147C3DD45E42478038FC347CCB65FE02BC2B4834@XCH-MW-08V.mw.nos.boeing.com>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com> <4FB1B592.1090706@jacni.com>, <B0147C3DD45E42478038FC347CCB65FE02BB90F50B@XCH-MW-08V.mw.nos.boeing.com> <B641703E-A8F1-4B12-9679-4D72F81C6A45@huawei.com>
In-Reply-To: <B641703E-A8F1-4B12-9679-4D72F81C6A45@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_B0147C3DD45E42478038FC347CCB65FE02BC2B4834XCHMW08Vmwnos_"
MIME-Version: 1.0
X-TM-AS-MML: No
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 24 May 2012 20:02:10 -0000

--_000_B0147C3DD45E42478038FC347CCB65FE02BC2B4834XCHMW08Vmwnos_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Tina, yes, that sounds good to me. I think theoretical approaches that have=
 little practical value, like trying to backfit an IPv4 device to do IPv6 M=
LD and then IPv6 to IPv4 packet translation, end up creating more confusion=
 than explaining anything, IMO.

Also, for multicast, I would think that the provider can control address ma=
pping regardless of whether the source is under his control or not? In some=
 cases, the provider may not need to, especially with IPv6 to IPv6 multicas=
ts, but that aside, the ISP should always be able to map IP multicast group=
s from a source to some other multicast address, no?

Bert

From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
Sent: Thursday, May 24, 2012 12:02 PM
To: Manfredi, Albert E
Cc: mboned@ietf.org
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01

Bert,
Thank you for your support.

What you are saying suggests that it is only the third part of the existing=
 document that makes real sense to an operator considering the problem of a=
ddress acquisition. Maybe the document has to be organized differently. Ins=
tead of looking at theoretical approaches to the problem, maybe it should l=
ook at what might work for specific operator scenarios. We could think abou=
t what are the relevant variables to describe these scenarios. Whether the =
source and receiver support the same IP version is obviously one aspect, an=
d whether the source is under the control of the provider (so that the prov=
ider can control address mapping.) Then there are the variations in archite=
cture for creation and provision of the EPG.

Does this seem to be on the right track?

Tina

On May 15, 2012, at 3:07 PM, "Manfredi, Albert E" <albert.e.manfredi@boeing=
.com<mailto:albert.e.manfredi@boeing.com>> wrote:
Tina et al,

I also support this effort. A couple of comments:

My reaction to the Reactive Strategy in 3.1 was that it's too hard. Instead=
 of making the IPv4 receiver kludge up IPv6 addresses, presumably kludge up=
 MLD(?), and then convert IPv6 multicasts, why not just install an IPv6 sta=
ck in that receiver? (And yet, the counter to this is that Microsoft Office=
 2003 is capable of ingesting Office 2007 files quite well, and maybe even =
Office 2010 files, and all done in the "receiver." Still, Office suites are=
 expensive for users, whereas IP stacks are not.)

The Dynamic Modification in 3.2, by the network, seems to be a more realist=
ic option.

The Administrative Preparation in 3.3 seems to be an elaboration of 3.2. It=
 merely adds a description of mechanisms that may be used to obtain info on=
 the receiver, where 3.2 only said:

   It requires that an element in that network must
   intercept program guide information destined to the receiver, locate
   the access information, and map IP addresses to an alternate version
   as necessary to suit the receiver.

Isn't 3.3 describing HOW the network knows to "suit the receiver"?

Another option would be for the network to transfer both multicasts, and si=
mply respond according to whether the receiver used IGMP or MLD to join the=
 multicast. And the receiver would know the appropriate IPv4 or IPv6 multic=
ast group (and potentially source IP) using OOB means, like the EPG itself,=
 or the EPG plus an associated SIP session, or EPG plus SDP. (Wasn't there =
a discussion some time ago about "why use SDP anymore?") Assuming bandwidth=
 isn't in very short supply, my own approach would be either to get both ve=
rsions from the source, or to create the other version at the initial ingre=
ss point to my network.

Bert


From: mboned-bounces@ietf.org<mailto:mboned-bounces@ietf.org> [mailto:mbone=
d-bounces@ietf.org] On Behalf Of Jacni Qin
Sent: Monday, May 14, 2012 9:47 PM
To: Tina TSOU
Cc: 'mboned@ietf.org<mailto:mboned@ietf.org>'
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01

Hi authors,

Some questions about the "possible solutions" proposed,

3.1, as stated by itself, probably not reasonable from implementation stand=
point.

For 3.2 and the first approach in 3.3, I guess they're ALGs, and IMHO, the =
discussions in Section 4.1 of the http://tools.ietf.org/html/draft-ietf-mbo=
ned-v4v6-mcast-ps-00, are sufficient.

About the second approach in 3.3, not sure I fully understand it yet, but s=
o far I see it also a kind of ALG.


Cheers,
Jacni

On 5/11/2012 Friday 1:49 AM, Tina TSOU wrote:
Dear chairs,
Would you ask the WG for adoption of draft-tsou-mboned-multrans-addr-acquis=
ition-01 as WG document?

Thank you and have a good day.

Tina and co-authors

From: Tina TSOU
Sent: Wednesday, May 02, 2012 11:58 AM
To: mboned@ietf.org<mailto:mboned@ietf.org>
Subject: draft-tsou-mboned-multrans-addr-acquisition-01


Now that the multicast transition framework document is officially accepted=
, is the Working Group prepared also to take on the topic of address acquis=
ition, which is one of the tasks it identifies?
If so, would draft-tsou-mboned-multrans-addr-acquisition-01 be acceptable a=
s a starting point?

Tina






_______________________________________________

MBONED mailing list

MBONED@ietf.org<mailto:MBONED@ietf.org>

https://www.ietf.org/mailman/listinfo/mboned

--_000_B0147C3DD45E42478038FC347CCB65FE02BC2B4834XCHMW08Vmwnos_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Times New Roman","serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle26
	{mso-style-type:personal-reply;
	font-family:"Times New Roman","serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite lang=3DEN-US=
 link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>=
<span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color=
:blue'>Tina, yes, that sounds good to me. I think theoretical approaches th=
at have little practical value, like trying to backfit an IPv4 device to do=
 IPv6 MLD and then IPv6 to IPv4 packet translation, end up creating more co=
nfusion than explaining anything, IMO.<o:p></o:p></span></p><p class=3DMsoN=
ormal><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"=
;color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:blue'>Also=
, for multicast, I would think that the provider can control address mappin=
g regardless of whether the source is under his control or not? In some cas=
es, the provider may not need to, especially with IPv6 to IPv6 multicasts, =
but that aside, the ISP should always be able to map IP multicast groups fr=
om a source to some other multicast address, no?<o:p></o:p></span></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New Roma=
n","serif";color:blue'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><sp=
an style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:bl=
ue'>Bert<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:12.0pt;font-family:"Times New Roman","serif";color:blue'><o:p>&nbsp;</o:p>=
</span></p><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;pa=
dding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:1=
0.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><=
span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:wind=
owtext'> Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com] <br><b>Sent:</b> T=
hursday, May 24, 2012 12:02 PM<br><b>To:</b> Manfredi, Albert E<br><b>Cc:</=
b> mboned@ietf.org<br><b>Subject:</b> Re: [MBONED] draft-tsou-mboned-multra=
ns-addr-acquisition-01<o:p></o:p></span></p></div></div><p class=3DMsoNorma=
l><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Bert,&nbsp;<o:p></o:p></p>=
</div><div><p class=3DMsoNormal>Thank you for your support.<o:p></o:p></p><=
/div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DM=
soNormal>What you are saying suggests that it is only the third part of the=
 existing document that makes real sense to an operator considering the pro=
blem of address acquisition. Maybe the document has to be organized differe=
ntly. Instead of looking at theoretical approaches to the problem, maybe it=
 should look at what might work for specific operator scenarios. We could t=
hink about what are the relevant variables to describe these scenarios. Whe=
ther the source and receiver support the same IP version is obviously one a=
spect, and whether the source is under the control of the provider (so that=
 the provider can control address mapping.) Then there are the variations i=
n architecture for creation and provision of the EPG.<br><br>Does this seem=
 to be on the right track?<br><br>Tina<o:p></o:p></p></div><div><p class=3D=
MsoNormal style=3D'margin-bottom:12.0pt'><br>On May 15, 2012, at 3:07 PM, &=
quot;Manfredi, Albert E&quot; &lt;<a href=3D"mailto:albert.e.manfredi@boein=
g.com">albert.e.manfredi@boeing.com</a>&gt; wrote:<o:p></o:p></p></div><blo=
ckquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=3DMsoN=
ormal><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"=
;color:blue'>Tina et al,</span><o:p></o:p></p><p class=3DMsoNormal><span st=
yle=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:blue'>&=
nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:12=
.0pt;font-family:"Times New Roman","serif";color:blue'>I also support this =
effort. A couple of comments:</span><o:p></o:p></p><p class=3DMsoNormal><sp=
an style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:bl=
ue'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-si=
ze:12.0pt;font-family:"Times New Roman","serif";color:blue'>My reaction to =
the Reactive Strategy in 3.1 was that it&#8217;s too hard. Instead of makin=
g the IPv4 receiver kludge up IPv6 addresses, presumably kludge up MLD(?), =
and then convert IPv6 multicasts, why not just install an IPv6 stack in tha=
t receiver? (And yet, the counter to this is that Microsoft Office 2003 is =
capable of ingesting Office 2007 files quite well, and maybe even Office 20=
10 files, and all done in the &#8220;receiver.&#8221; Still, Office suites =
are expensive for users, whereas IP stacks are not.)</span><o:p></o:p></p><=
p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:blue'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal=
><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";colo=
r:blue'>The Dynamic Modification in 3.2, by the network, seems to be a more=
 realistic option.</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D=
'font-size:12.0pt;font-family:"Times New Roman","serif";color:blue'>&nbsp;<=
/span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;f=
ont-family:"Times New Roman","serif";color:blue'>The Administrative Prepara=
tion in 3.3 seems to be an elaboration of 3.2. It merely adds a description=
 of mechanisms that may be used to obtain info on the receiver, where 3.2 o=
nly said:</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-siz=
e:12.0pt;font-family:"Times New Roman","serif";color:blue'>&nbsp;</span><o:=
p></o:p></p><p class=3DMsoNormal style=3D'line-height:14.4pt'><span style=
=3D'font-size:10.0pt;font-family:"Courier New";color:windowtext'>&nbsp;&nbs=
p; It requires that an element in that network must</span><o:p></o:p></p><p=
 class=3DMsoNormal style=3D'line-height:14.4pt'><span style=3D'font-size:10=
.0pt;font-family:"Courier New";color:windowtext'>&nbsp;&nbsp; intercept pro=
gram guide information destined to the receiver, locate</span><o:p></o:p></=
p><p class=3DMsoNormal style=3D'line-height:14.4pt'><span style=3D'font-siz=
e:10.0pt;font-family:"Courier New";color:windowtext'>&nbsp;&nbsp; the acces=
s information, and map IP addresses to an alternate version</span><o:p></o:=
p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Cou=
rier New";color:windowtext'>&nbsp;&nbsp; as necessary to suit the receiver.=
</span><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif=
";color:blue'> </span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'fo=
nt-size:12.0pt;font-family:"Times New Roman","serif";color:blue'>&nbsp;</sp=
an><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font=
-family:"Times New Roman","serif";color:blue'>Isn&#8217;t 3.3 describing HO=
W the network knows to &#8220;suit the receiver&#8221;?</span><o:p></o:p></=
p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Times N=
ew Roman","serif";color:blue'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNor=
mal><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";c=
olor:blue'>Another option would be for the network to transfer both multica=
sts, and simply respond according to whether the receiver used IGMP or MLD =
to join the multicast. And the receiver would know the appropriate IPv4 or =
IPv6 multicast group (and potentially source IP) using OOB means, like the =
EPG itself, or the EPG plus an associated SIP session, or EPG plus SDP. (Wa=
sn&#8217;t there a discussion some time ago about &#8220;why use SDP anymor=
e?&#8221;) Assuming bandwidth isn&#8217;t in very short supply, my own appr=
oach would be either to get both versions from the source, or to create the=
 other version at the initial ingress point to my network.</span><o:p></o:p=
></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Time=
s New Roman","serif";color:blue'>&nbsp;</span><o:p></o:p></p><p class=3DMso=
Normal><span style=3D'font-size:12.0pt;font-family:"Times New Roman","serif=
";color:blue'>Bert</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D=
'font-size:12.0pt;font-family:"Times New Roman","serif";color:blue'>&nbsp;<=
/span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;f=
ont-family:"Times New Roman","serif";color:blue'>&nbsp;</span><o:p></o:p></=
p><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0=
pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;fon=
t-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span styl=
e=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> =
<a href=3D"mailto:mboned-bounces@ietf.org">mboned-bounces@ietf.org</a> [<a =
href=3D"mailto:mboned-bounces@ietf.org">mailto:mboned-bounces@ietf.org</a>]=
 <b>On Behalf Of </b>Jacni Qin<br><b>Sent:</b> Monday, May 14, 2012 9:47 PM=
<br><b>To:</b> Tina TSOU<br><b>Cc:</b> '<a href=3D"mailto:mboned@ietf.org">=
mboned@ietf.org</a>'<br><b>Subject:</b> Re: [MBONED] draft-tsou-mboned-mult=
rans-addr-acquisition-01</span><o:p></o:p></p></div></div><p class=3DMsoNor=
mal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>Hi authors,<br><br>Some quest=
ions about the &quot;possible solutions&quot; proposed,<br><br>3.1, as stat=
ed by itself, probably not reasonable from implementation standpoint.<br><b=
r>For 3.2 and the first approach in 3.3, I guess they're ALGs, and IMHO, th=
e discussions in Section 4.1 of the <a href=3D"http://tools.ietf.org/html/d=
raft-ietf-mboned-v4v6-mcast-ps-00">http://tools.ietf.org/html/draft-ietf-mb=
oned-v4v6-mcast-ps-00</a>, are sufficient.<br><br>About the second approach=
 in 3.3, not sure I fully understand it yet, but so far I see it also a kin=
d of ALG.<br><br><br>Cheers,<br>Jacni<br><br>On 5/11/2012 Friday 1:49 AM, T=
ina TSOU wrote: <o:p></o:p></p><p class=3DMsoNormal><span style=3D'color:#1=
F497D'>Dear chairs,</span><o:p></o:p></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'>Would you ask the WG for adoption of draft-tsou-mboned-m=
ultrans-addr-acquisition-01 as WG document?</span><o:p></o:p></p><p class=
=3DMsoNormal><span style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><p c=
lass=3DMsoNormal><span style=3D'color:#1F497D'>Thank you and have a good da=
y.</span><o:p></o:p></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>=
&nbsp;</span><o:p></o:p></p><div><p class=3DMsoNormal><span style=3D'color:=
#1F497D'>Tina and co-authors</span><o:p></o:p></p></div><p class=3DMsoNorma=
l><span style=3D'color:#1F497D'>&nbsp;</span><o:p></o:p></p><div style=3D'b=
order:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><di=
v style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in=
 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"=
Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-=
family:"Tahoma","sans-serif"'> Tina TSOU <br><b>Sent:</b> Wednesday, May 02=
, 2012 11:58 AM<br><b>To:</b> <a href=3D"mailto:mboned@ietf.org">mboned@iet=
f.org</a><br><b>Subject:</b> draft-tsou-mboned-multrans-addr-acquisition-01=
</span><o:p></o:p></p></div></div><p class=3DMsoNormal>&nbsp;<o:p></o:p></p=
><p class=3DMsoPlainText>Now that the multicast transition framework docume=
nt is officially accepted, is the Working Group prepared also to take on th=
e topic of address acquisition, which is one of the tasks it identifies?<o:=
p></o:p></p><p class=3DMsoNormal>If so, would draft-tsou-mboned-multrans-ad=
dr-acquisition-01 be acceptable as a starting point?<o:p></o:p></p><p class=
=3DMsoNormal>&nbsp;<o:p></o:p></p><p class=3DMsoNormal>Tina<o:p></o:p></p><=
p class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><p class=3DMsoNormal><span s=
tyle=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><br><br><br=
><br></span><o:p></o:p></p><pre>___________________________________________=
____<o:p></o:p></pre><pre>MBONED mailing list<o:p></o:p></pre><pre><a href=
=3D"mailto:MBONED@ietf.org">MBONED@ietf.org</a><o:p></o:p></pre><pre><a hre=
f=3D"https://www.ietf.org/mailman/listinfo/mboned">https://www.ietf.org/mai=
lman/listinfo/mboned</a><o:p></o:p></pre></div></blockquote></div></body></=
html>=

--_000_B0147C3DD45E42478038FC347CCB65FE02BC2B4834XCHMW08Vmwnos_--


From Tina.Tsou.Zouting@huawei.com  Thu May 24 20:15:23 2012
Return-Path: <Tina.Tsou.Zouting@huawei.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 C634611E80C2 for <mboned@ietfa.amsl.com>; Thu, 24 May 2012 20:15:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.278
X-Spam-Level: 
X-Spam-Status: No, score=-6.278 tagged_above=-999 required=5 tests=[AWL=0.320,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 9Z8I-Lw17Ns7 for <mboned@ietfa.amsl.com>; Thu, 24 May 2012 20:15:22 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 8043E11E8097 for <mboned@ietf.org>; Thu, 24 May 2012 20:15:22 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AGM99953; Thu, 24 May 2012 23:15:22 -0400 (EDT)
Received: from DFWEML403-HUB.china.huawei.com (10.193.5.151) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 24 May 2012 20:11:45 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.80]) by dfweml403-hub.china.huawei.com ([10.193.5.151]) with mapi id 14.01.0323.003; Thu, 24 May 2012 20:11:48 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Thread-Topic: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
Thread-Index: Ac0olW4tpAJfzZWwTw2lKRKI4vlTgAGPwEowAOi2jQAAKqIPgAGpLR8WAAgXMTAAD08m7w==
Date: Fri, 25 May 2012 03:11:48 +0000
Message-ID: <20437CFB-5367-40AB-8CD3-A7988F5400BF@huawei.com>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com> <4FB1B592.1090706@jacni.com>, <B0147C3DD45E42478038FC347CCB65FE02BB90F50B@XCH-MW-08V.mw.nos.boeing.com> <B641703E-A8F1-4B12-9679-4D72F81C6A45@huawei.com>, <B0147C3DD45E42478038FC347CCB65FE02BC2B4834@XCH-MW-08V.mw.nos.boeing.com>
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE02BC2B4834@XCH-MW-08V.mw.nos.boeing.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_20437CFB536740AB8CD3A7988F5400BFhuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 25 May 2012 03:15:23 -0000

--_000_20437CFB536740AB8CD3A7988F5400BFhuaweicom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

I had in mind some interaction between the translations used in the signall=
ing and data planes and the translation used in the EPG, but as you say, th=
e operator can always re-translate if necessary.

Tina

On May 24, 2012, at 1:02 PM, "Manfredi, Albert E" <albert.e.manfredi@boeing=
.com<mailto:albert.e.manfredi@boeing.com>> wrote:

Tina, yes, that sounds good to me. I think theoretical approaches that have=
 little practical value, like trying to backfit an IPv4 device to do IPv6 M=
LD and then IPv6 to IPv4 packet translation, end up creating more confusion=
 than explaining anything, IMO.

Also, for multicast, I would think that the provider can control address ma=
pping regardless of whether the source is under his control or not? In some=
 cases, the provider may not need to, especially with IPv6 to IPv6 multicas=
ts, but that aside, the ISP should always be able to map IP multicast group=
s from a source to some other multicast address, no?

Bert

From: Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
Sent: Thursday, May 24, 2012 12:02 PM
To: Manfredi, Albert E
Cc: mboned@ietf.org<mailto:mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01

Bert,
Thank you for your support.

What you are saying suggests that it is only the third part of the existing=
 document that makes real sense to an operator considering the problem of a=
ddress acquisition. Maybe the document has to be organized differently. Ins=
tead of looking at theoretical approaches to the problem, maybe it should l=
ook at what might work for specific operator scenarios. We could think abou=
t what are the relevant variables to describe these scenarios. Whether the =
source and receiver support the same IP version is obviously one aspect, an=
d whether the source is under the control of the provider (so that the prov=
ider can control address mapping.) Then there are the variations in archite=
cture for creation and provision of the EPG.

Does this seem to be on the right track?

Tina

On May 15, 2012, at 3:07 PM, "Manfredi, Albert E" <albert.e.manfredi@boeing=
.com<mailto:albert.e.manfredi@boeing.com>> wrote:
Tina et al,

I also support this effort. A couple of comments:

My reaction to the Reactive Strategy in 3.1 was that it=92s too hard. Inste=
ad of making the IPv4 receiver kludge up IPv6 addresses, presumably kludge =
up MLD(?), and then convert IPv6 multicasts, why not just install an IPv6 s=
tack in that receiver? (And yet, the counter to this is that Microsoft Offi=
ce 2003 is capable of ingesting Office 2007 files quite well, and maybe eve=
n Office 2010 files, and all done in the =93receiver.=94 Still, Office suit=
es are expensive for users, whereas IP stacks are not.)

The Dynamic Modification in 3.2, by the network, seems to be a more realist=
ic option.

The Administrative Preparation in 3.3 seems to be an elaboration of 3.2. It=
 merely adds a description of mechanisms that may be used to obtain info on=
 the receiver, where 3.2 only said:

   It requires that an element in that network must
   intercept program guide information destined to the receiver, locate
   the access information, and map IP addresses to an alternate version
   as necessary to suit the receiver.

Isn=92t 3.3 describing HOW the network knows to =93suit the receiver=94?

Another option would be for the network to transfer both multicasts, and si=
mply respond according to whether the receiver used IGMP or MLD to join the=
 multicast. And the receiver would know the appropriate IPv4 or IPv6 multic=
ast group (and potentially source IP) using OOB means, like the EPG itself,=
 or the EPG plus an associated SIP session, or EPG plus SDP. (Wasn=92t ther=
e a discussion some time ago about =93why use SDP anymore?=94) Assuming ban=
dwidth isn=92t in very short supply, my own approach would be either to get=
 both versions from the source, or to create the other version at the initi=
al ingress point to my network.

Bert


From: mboned-bounces@ietf.org<mailto:mboned-bounces@ietf.org> [mailto:mbone=
d-bounces@ietf.org] On Behalf Of Jacni Qin
Sent: Monday, May 14, 2012 9:47 PM
To: Tina TSOU
Cc: 'mboned@ietf.org<mailto:mboned@ietf.org>'
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01

Hi authors,

Some questions about the "possible solutions" proposed,

3.1, as stated by itself, probably not reasonable from implementation stand=
point.

For 3.2 and the first approach in 3.3, I guess they're ALGs, and IMHO, the =
discussions in Section 4.1 of the http://tools.ietf.org/html/draft-ietf-mbo=
ned-v4v6-mcast-ps-00, are sufficient.

About the second approach in 3.3, not sure I fully understand it yet, but s=
o far I see it also a kind of ALG.


Cheers,
Jacni

On 5/11/2012 Friday 1:49 AM, Tina TSOU wrote:
Dear chairs,
Would you ask the WG for adoption of draft-tsou-mboned-multrans-addr-acquis=
ition-01 as WG document?

Thank you and have a good day.

Tina and co-authors

From: Tina TSOU
Sent: Wednesday, May 02, 2012 11:58 AM
To: mboned@ietf.org<mailto:mboned@ietf.org>
Subject: draft-tsou-mboned-multrans-addr-acquisition-01


Now that the multicast transition framework document is officially accepted=
, is the Working Group prepared also to take on the topic of address acquis=
ition, which is one of the tasks it identifies?
If so, would draft-tsou-mboned-multrans-addr-acquisition-01 be acceptable a=
s a starting point?

Tina






_______________________________________________

MBONED mailing list

MBONED@ietf.org<mailto:MBONED@ietf.org>

https://www.ietf.org/mailman/listinfo/mboned

--_000_20437CFB536740AB8CD3A7988F5400BFhuaweicom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body bgcolor=3D"#FFFFFF">
<div>I had in mind some interaction between the translations used in the si=
gnalling and data planes and the translation used in the EPG, but as you sa=
y, the operator can always re-translate if necessary.<br>
<br>
Tina&nbsp;</div>
<div><br>
On May 24, 2012, at 1:02 PM, &quot;Manfredi, Albert E&quot; &lt;<a href=3D"=
mailto:albert.e.manfredi@boeing.com">albert.e.manfredi@boeing.com</a>&gt; w=
rote:<br>
<br>
</div>
<div></div>
<blockquote type=3D"cite">
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;
	color:black;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	color:black;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle25
	{mso-style-type:personal;
	font-family:"Times New Roman","serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle26
	{mso-style-type:personal-reply;
	font-family:"Times New Roman","serif";
	color:blue;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">Tina, yes, that sounds go=
od to me. I think theoretical approaches that have little practical value, =
like trying to backfit an IPv4 device to do IPv6 MLD and
 then IPv6 to IPv4 packet translation, end up creating more confusion than =
explaining anything, IMO.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">Also, for multicast, I wo=
uld think that the provider can control address mapping regardless of wheth=
er the source is under his control or not? In some cases,
 the provider may not need to, especially with IPv6 to IPv6 multicasts, but=
 that aside, the ISP should always be able to map IP multicast groups from =
a source to some other multicast address, no?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">Bert<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext"> Tina TSOU [mailto:Tina.Tsou.Zouting@huawei.com]
<br>
<b>Sent:</b> Thursday, May 24, 2012 12:02 PM<br>
<b>To:</b> Manfredi, Albert E<br>
<b>Cc:</b> <a href=3D"mailto:mboned@ietf.org">mboned@ietf.org</a><br>
<b>Subject:</b> Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01=
<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Bert,&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Thank you for your support.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">What you are saying suggests that it is only the thi=
rd part of the existing document that makes real sense to an operator consi=
dering the problem of address acquisition. Maybe the document has to be org=
anized differently. Instead of looking
 at theoretical approaches to the problem, maybe it should look at what mig=
ht work for specific operator scenarios. We could think about what are the =
relevant variables to describe these scenarios. Whether the source and rece=
iver support the same IP version
 is obviously one aspect, and whether the source is under the control of th=
e provider (so that the provider can control address mapping.) Then there a=
re the variations in architecture for creation and provision of the EPG.<br=
>
<br>
Does this seem to be on the right track?<br>
<br>
Tina<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
On May 15, 2012, at 3:07 PM, &quot;Manfredi, Albert E&quot; &lt;<a href=3D"=
mailto:albert.e.manfredi@boeing.com">albert.e.manfredi@boeing.com</a>&gt; w=
rote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">Tina et al,</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">I also support this effor=
t. A couple of comments:</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">My reaction to the Reacti=
ve Strategy in 3.1 was that it=92s too hard. Instead of making the IPv4 rec=
eiver kludge up IPv6 addresses, presumably kludge up MLD(?),
 and then convert IPv6 multicasts, why not just install an IPv6 stack in th=
at receiver? (And yet, the counter to this is that Microsoft Office 2003 is=
 capable of ingesting Office 2007 files quite well, and maybe even Office 2=
010 files, and all done in the =93receiver.=94
 Still, Office suites are expensive for users, whereas IP stacks are not.)<=
/span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">The Dynamic Modification =
in 3.2, by the network, seems to be a more realistic option.</span><o:p></o=
:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">The Administrative Prepar=
ation in 3.3 seems to be an elaboration of 3.2. It merely adds a descriptio=
n of mechanisms that may be used to obtain info on the receiver,
 where 3.2 only said:</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:windowtext">&nbsp;&nbsp;=
 It requires that an element in that network must</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:windowtext">&nbsp;&nbsp;=
 intercept program guide information destined to the receiver, locate</span=
><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"line-height:14.4pt"><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Courier New&quot;;color:windowtext">&nbsp;&nbsp;=
 the access information, and map IP addresses to an alternate version</span=
><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:windowtext">&nbsp;&nbsp; as necessary to suit the rec=
eiver.</span><span style=3D"font-size:12.0pt;font-family:&quot;Times New Ro=
man&quot;,&quot;serif&quot;;color:blue">
</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">Isn=92t 3.3 describing HO=
W the network knows to =93suit the receiver=94?</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">Another option would be f=
or the network to transfer both multicasts, and simply respond according to=
 whether the receiver used IGMP or MLD to join the multicast.
 And the receiver would know the appropriate IPv4 or IPv6 multicast group (=
and potentially source IP) using OOB means, like the EPG itself, or the EPG=
 plus an associated SIP session, or EPG plus SDP. (Wasn=92t there a discuss=
ion some time ago about =93why use SDP
 anymore?=94) Assuming bandwidth isn=92t in very short supply, my own appro=
ach would be either to get both versions from the source, or to create the =
other version at the initial ingress point to my network.</span><o:p></o:p>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">Bert</span><o:p></o:p></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">&nbsp;</span><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;color:blue">&nbsp;</span><o:p></o:p><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext">From:</span></b><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif=
&quot;;color:windowtext">
<a href=3D"mailto:mboned-bounces@ietf.org">mboned-bounces@ietf.org</a> [<a =
href=3D"mailto:mboned-bounces@ietf.org">mailto:mboned-bounces@ietf.org</a>]
<b>On Behalf Of </b>Jacni Qin<br>
<b>Sent:</b> Monday, May 14, 2012 9:47 PM<br>
<b>To:</b> Tina TSOU<br>
<b>Cc:</b> '<a href=3D"mailto:mboned@ietf.org">mboned@ietf.org</a>'<br>
<b>Subject:</b> Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01=
</span><o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Hi authors,<br>
<br>
Some questions about the &quot;possible solutions&quot; proposed,<br>
<br>
3.1, as stated by itself, probably not reasonable from implementation stand=
point.<br>
<br>
For 3.2 and the first approach in 3.3, I guess they're ALGs, and IMHO, the =
discussions in Section 4.1 of the
<a href=3D"http://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00">h=
ttp://tools.ietf.org/html/draft-ietf-mboned-v4v6-mcast-ps-00</a>, are suffi=
cient.<br>
<br>
About the second approach in 3.3, not sure I fully understand it yet, but s=
o far I see it also a kind of ALG.<br>
<br>
<br>
Cheers,<br>
Jacni<br>
<br>
On 5/11/2012 Friday 1:49 AM, Tina TSOU wrote: <o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Dear chairs,</span><o:=
p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Would you ask the WG f=
or adoption of draft-tsou-mboned-multrans-addr-acquisition-01 as WG documen=
t?</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thank you and have a g=
ood day.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Tina and co-authors</s=
pan><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Tina TSO=
U
<br>
<b>Sent:</b> Wednesday, May 02, 2012 11:58 AM<br>
<b>To:</b> <a href=3D"mailto:mboned@ietf.org">mboned@ietf.org</a><br>
<b>Subject:</b> draft-tsou-mboned-multrans-addr-acquisition-01</span><o:p><=
/o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoPlainText">Now that the multicast transition framework docum=
ent is officially accepted, is the Working Group prepared also to take on t=
he topic of address acquisition, which is one of the tasks it identifies?<o=
:p></o:p></p>
<p class=3D"MsoNormal">If so, would draft-tsou-mboned-multrans-addr-acquisi=
tion-01 be acceptable as a starting point?<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Tina<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;"><br>
<br>
<br>
<br>
</span><o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>MBONED mailing list<o:p></o:p></pre>
<pre><a href=3D"mailto:MBONED@ietf.org">MBONED@ietf.org</a><o:p></o:p></pre=
>
<pre><a href=3D"https://www.ietf.org/mailman/listinfo/mboned">https://www.i=
etf.org/mailman/listinfo/mboned</a><o:p></o:p></pre>
</div>
</blockquote>
</div>
</div>
</blockquote>
</body>
</html>

--_000_20437CFB536740AB8CD3A7988F5400BFhuaweicom_--

From bingxuere@gmail.com  Mon May 28 02:27:03 2012
Return-Path: <bingxuere@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 25EE921F8595 for <mboned@ietfa.amsl.com>; Mon, 28 May 2012 02:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 jrw5wPSkfGJO for <mboned@ietfa.amsl.com>; Mon, 28 May 2012 02:27:02 -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 53DE121F858D for <mboned@ietf.org>; Mon, 28 May 2012 02:27:02 -0700 (PDT)
Received: by yenq13 with SMTP id q13so1471513yen.31 for <mboned@ietf.org>; Mon, 28 May 2012 02:27:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7clelMidHtPvm+Jt48QWGEPFaGo+FoMGWHsqelAUVPk=; b=seXEh7d3FhRDuJw1TDzW/O/ocD/unm8jpgxHFIMIL+VhJm3nfxfSjLBksPWx5lWc9X Yb2s9mqeNrkVMp4DahNPmzp5B5eHqct8AEDmVPsr2KYdy9Gn3WTjXfECQYf7n90zDa/J RzqOU7tBjag0+emzGkOj4Ec1pi2YGaPDdulrrzke3CvVsjtx4CT7Y9E7prtWA2Rhf8Rb Ri6xMsKHIfKJPN4HAprpMC/HIvnRAdG2AIRucFEzbStcUVklA1xBcQvlDR1at7VmssrR mUVjJ2sj7TqsBOKwN2S7DX/9TXV8/CMEhfLoKUej+ow1yBPDLk5YkFGGdV2llaD3LUGX Dr4Q==
Received: by 10.50.158.161 with SMTP id wv1mr3990611igb.43.1338197221629; Mon, 28 May 2012 02:27:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.46.6 with HTTP; Mon, 28 May 2012 02:26:21 -0700 (PDT)
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E2A52D2C0@PUEXCB1B.nanterre.francetelecom.fr>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com> <20120514132102.U91557@eng-mail01.juniper.net> <94C682931C08B048B7A8645303FDC9F36E2A52D2C0@PUEXCB1B.nanterre.francetelecom.fr>
From: Qiong <bingxuere@gmail.com>
Date: Mon, 28 May 2012 17:26:21 +0800
Message-ID: <CAH3bfAC8Gf+0yn7My7onOEWw222F_586XfcUEK_CeNhOBZ49SA@mail.gmail.com>
To: mohamed.boucadair@orange.com
Content-Type: multipart/alternative; boundary=14dae9340c7508df2d04c1155270
Cc: MBONED WG <mboned@ietf.org>
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 28 May 2012 09:27:03 -0000

--14dae9340c7508df2d04c1155270
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Dear all,

I support the adoption for this document. I do think it would be a usable
extension to SDP.

Best wishes
Qiong

On Tue, May 15, 2012 at 7:30 PM, <mohamed.boucadair@orange.com> wrote:

> Dear all,
>
> I do personally see a value to publish this document as a WG it; mainly
> the discussion about potential extension to SDP to convey both IPv4 and
> IPv6 addresses.
>
> I support the adoption of this document.
>
> Cheers,
> Med
>
> >-----Message d'origine-----
> >De : mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org]
> >De la part de Leonard Giuliano
> >Envoy=C3=A9 : lundi 14 mai 2012 22:24
> >=C3=80 : MBONED WG
> >Objet : Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
> >
> >
> >We would like to poll the WG to decide if
> >draft-tsou-mboned-multrans-addr-acquisition-01 should be adopted as an
> >MBONED document.  Please respnd by May 29 if you thing this
> >doc should or
> >should not be adopted by MBONED.
> >
> >
> >-MBONED Chairs
> >
> >
> >On Thu, 10 May 2012, Tina TSOU wrote:
> >
> >-) Dear chairs,
> >-) Would you ask the WG for adoption of
> >draft-tsou-mboned-multrans-addr-acquisition-01 as WG document?
> >-)
> >-) Thank you and have a good day.
> >-)
> >-) Tina and co-authors
> >-)
> >-) From: Tina TSOU
> >-) Sent: Wednesday, May 02, 2012 11:58 AM
> >-) To: mboned@ietf.org
> >-) Subject: draft-tsou-mboned-multrans-addr-acquisition-01
> >-)
> >-)
> >-) Now that the multicast transition framework document is
> >officially accepted, is the Working Group prepared also to
> >take on the topic of address acquisition, which is one of the
> >tasks it identifies?
> >-) If so, would draft-tsou-mboned-multrans-addr-acquisition-01
> >be acceptable as a starting point?
> >-)
> >-) Tina
> >-)
> >-)
> >_______________________________________________
> >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
>

--14dae9340c7508df2d04c1155270
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Dear all,<br><br>I support the adoption for this document. I do think it wo=
uld be a usable extension to SDP.<br><br>Best wishes<br>Qiong<br><br><div c=
lass=3D"gmail_quote">On Tue, May 15, 2012 at 7:30 PM,  <span dir=3D"ltr">&l=
t;<a href=3D"mailto:mohamed.boucadair@orange.com" target=3D"_blank">mohamed=
.boucadair@orange.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Dear all,<br>
<br>
I do personally see a value to publish this document as a WG it; mainly the=
 discussion about potential extension to SDP to convey both IPv4 and IPv6 a=
ddresses.<br>
<br>
I support the adoption of this document.<br>
<br>
Cheers,<br>
Med<br>
<br>
&gt;-----Message d&#39;origine-----<br>
&gt;De : <a href=3D"mailto:mboned-bounces@ietf.org">mboned-bounces@ietf.org=
</a> [mailto:<a href=3D"mailto:mboned-bounces@ietf.org">mboned-bounces@ietf=
.org</a>]<br>
&gt;De la part de Leonard Giuliano<br>
&gt;Envoy=C3=A9 : lundi 14 mai 2012 22:24<br>
&gt;=C3=80 : MBONED WG<br>
&gt;Objet : Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01<br>
<div class=3D"HOEnZb"><div class=3D"h5">&gt;<br>
&gt;<br>
&gt;We would like to poll the WG to decide if<br>
&gt;draft-tsou-mboned-multrans-addr-acquisition-01 should be adopted as an<=
br>
&gt;MBONED document. =C2=A0Please respnd by May 29 if you thing this<br>
&gt;doc should or<br>
&gt;should not be adopted by MBONED.<br>
&gt;<br>
&gt;<br>
&gt;-MBONED Chairs<br>
&gt;<br>
&gt;<br>
&gt;On Thu, 10 May 2012, Tina TSOU wrote:<br>
&gt;<br>
&gt;-) Dear chairs,<br>
&gt;-) Would you ask the WG for adoption of<br>
&gt;draft-tsou-mboned-multrans-addr-acquisition-01 as WG document?<br>
&gt;-)<br>
&gt;-) Thank you and have a good day.<br>
&gt;-)<br>
&gt;-) Tina and co-authors<br>
&gt;-)<br>
&gt;-) From: Tina TSOU<br>
&gt;-) Sent: Wednesday, May 02, 2012 11:58 AM<br>
&gt;-) To: <a href=3D"mailto:mboned@ietf.org">mboned@ietf.org</a><br>
&gt;-) Subject: draft-tsou-mboned-multrans-addr-acquisition-01<br>
&gt;-)<br>
&gt;-)<br>
&gt;-) Now that the multicast transition framework document is<br>
&gt;officially accepted, is the Working Group prepared also to<br>
&gt;take on the topic of address acquisition, which is one of the<br>
&gt;tasks it identifies?<br>
&gt;-) If so, would draft-tsou-mboned-multrans-addr-acquisition-01<br>
&gt;be acceptable as a starting point?<br>
&gt;-)<br>
&gt;-) Tina<br>
&gt;-)<br>
&gt;-)<br>
&gt;_______________________________________________<br>
&gt;MBONED mailing list<br>
&gt;<a href=3D"mailto:MBONED@ietf.org">MBONED@ietf.org</a><br>
&gt;<a href=3D"https://www.ietf.org/mailman/listinfo/mboned" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/mboned</a><br>
&gt;<br>
_______________________________________________<br>
MBONED mailing list<br>
<a href=3D"mailto:MBONED@ietf.org">MBONED@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mboned" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mboned</a><br>
</div></div></blockquote></div><br>

--14dae9340c7508df2d04c1155270--

From jiangsheng@huawei.com  Mon May 28 21:02:15 2012
Return-Path: <jiangsheng@huawei.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 AFA9121F878A for <mboned@ietfa.amsl.com>; Mon, 28 May 2012 21:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 zxbkH58u3CCB for <mboned@ietfa.amsl.com>; Mon, 28 May 2012 21:02:15 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 14B9D21F877D for <mboned@ietf.org>; Mon, 28 May 2012 21:02:15 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AGP85367; Tue, 29 May 2012 00:02:14 -0400 (EDT)
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 28 May 2012 20:59:19 -0700
Received: from SZXEML408-HUB.china.huawei.com (10.82.67.95) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 28 May 2012 20:59:21 -0700
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.40]) by szxeml408-hub.china.huawei.com ([10.82.67.95]) with mapi id 14.01.0323.003; Tue, 29 May 2012 11:59:17 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Leonard Giuliano <lenny@juniper.net>, MBONED WG <mboned@ietf.org>
Thread-Topic: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
Thread-Index: AQHNMg+kEWsp4gEAPEqfBHUi1wIoHZbKMgSAgBYIfxA=
Date: Tue, 29 May 2012 03:59:16 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B921EE6A44B@szxeml545-mbx.china.huawei.com>
References: <C0E0A32284495243BDE0AC8A066631A80C9B185E@szxeml526-mbs.china.huawei.com> <C0E0A32284495243BDE0AC8A066631A80C9CCCCE@szxeml526-mbs.china.huawei.com> <20120514132102.U91557@eng-mail01.juniper.net> <94C682931C08B048B7A8645303FDC9F36E2A52D2C0@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36E2A52D2C0@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.108.4.66]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 29 May 2012 04:02:15 -0000

+1, support the WG adoption.

Sheng

> -----Original Message-----
> From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On
> Behalf Of mohamed.boucadair@orange.com
> Sent: Tuesday, May 15, 2012 7:30 PM
> To: Leonard Giuliano; MBONED WG
> Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
>=20
> Dear all,
>=20
> I do personally see a value to publish this document as a WG it; mainly
> the discussion about potential extension to SDP to convey both IPv4 and
> IPv6 addresses.
>=20
> I support the adoption of this document.
>=20
> Cheers,
> Med
>=20
> >-----Message d'origine-----
> >De : mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org]
> >De la part de Leonard Giuliano
> >Envoy=E9 : lundi 14 mai 2012 22:24
> >=C0 : MBONED WG
> >Objet : Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
> >
> >
> >We would like to poll the WG to decide if
> >draft-tsou-mboned-multrans-addr-acquisition-01 should be adopted as an
> >MBONED document.  Please respnd by May 29 if you thing this
> >doc should or
> >should not be adopted by MBONED.
> >
> >
> >-MBONED Chairs
> >
> >
> >On Thu, 10 May 2012, Tina TSOU wrote:
> >
> >-) Dear chairs,
> >-) Would you ask the WG for adoption of
> >draft-tsou-mboned-multrans-addr-acquisition-01 as WG document?
> >-)
> >-) Thank you and have a good day.
> >-)
> >-) Tina and co-authors
> >-)
> >-) From: Tina TSOU
> >-) Sent: Wednesday, May 02, 2012 11:58 AM
> >-) To: mboned@ietf.org
> >-) Subject: draft-tsou-mboned-multrans-addr-acquisition-01
> >-)
> >-)
> >-) Now that the multicast transition framework document is
> >officially accepted, is the Working Group prepared also to
> >take on the topic of address acquisition, which is one of the
> >tasks it identifies?
> >-) If so, would draft-tsou-mboned-multrans-addr-acquisition-01
> >be acceptable as a starting point?
> >-)
> >-) Tina
> >-)
> >-)
> >_______________________________________________
> >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 xiechf01@gmail.com  Mon May 28 21:29:57 2012
Return-Path: <xiechf01@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 25DAA21F8717 for <mboned@ietfa.amsl.com>; Mon, 28 May 2012 21:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.845
X-Spam-Level: 
X-Spam-Status: No, score=-1.845 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, 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 WS7x94Mx+zQ9 for <mboned@ietfa.amsl.com>; Mon, 28 May 2012 21:29:56 -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 8423121F86EF for <mboned@ietf.org>; Mon, 28 May 2012 21:29:56 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so5281810pbc.31 for <mboned@ietf.org>; Mon, 28 May 2012 21:29:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:reply-to:subject:x-priority:x-has-attach:x-mailer :mime-version:message-id:content-type; bh=wMdZCorABtNdnV0cGynFq0/OCuiP27f2XYainjy0ZCY=; b=dBEob8tlDsX56fpWXleRPL+5xymJeYtzivipqdXKKf2M1KUlUAGkkA0vj5DSbechSn /HCFk2yGk3uoIqpqxqHETBt6Up+A86P+UL6ucIpC0LGUTGrPkp78K3GeduN5qkqlwYBD dXUq5kze4geze7h6V5fxn06uyz1DuwvgNmiWll2/QusAZgSUUkzVx0GNQ1sqY+vE7CvC l++rTHZf3Yfm1R0++5ZtDKxFsfGqkxjVTwUv3Q+0TmB1ZibCTnBsCjpzAJ89ug0Trv0H f4/BLAaKxX9plZ0Yp+yn7/fxNOU9d3+jCEgW24lK5jDwVjRbVYx5ygJ4uPxhN/oS0yRD kzLQ==
Received: by 10.68.131.35 with SMTP id oj3mr33582796pbb.156.1338265796058; Mon, 28 May 2012 21:29:56 -0700 (PDT)
Received: from xiechf-PC ([219.142.69.78]) by mx.google.com with ESMTPS id z2sm21460180pbv.34.2012.05.28.21.29.51 (version=SSLv3 cipher=OTHER); Mon, 28 May 2012 21:29:54 -0700 (PDT)
Date: Tue, 29 May 2012 12:29:51 +0800
From: xiechf01 <xiechf01@gmail.com>
To: mboned <mboned@ietf.org>,  mboned <mboned@ietf.org>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.91[cn]
Mime-Version: 1.0
Message-ID: <201205291229467375244@gmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart854745473772_=----"
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: xiechf01 <xiechf01@gmail.com>
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, 29 May 2012 04:29:57 -0000

This is a multi-part message in MIME format.

------=_001_NextPart854745473772_=----
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64

KzEgc3VwcG9ydA0KDQpDaG9uZ2ZlbmcgWGllDQoNCg0KDQoNCg0KDQotLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KRnJvbTogbWJvbmVkLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzptYm9uZWQt
Ym91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIExlb25hcmQgR2l1bGlhbm8NClNlbnQ6IFR1
ZXNkYXksIE1heSAxNSwgMjAxMiA0OjI0IEFNDQpUbzogTUJPTkVEIFdHDQpTdWJqZWN0OiBSZTog
W01CT05FRF0gZHJhZnQtdHNvdS1tYm9uZWQtbXVsdHJhbnMtYWRkci1hY3F1aXNpdGlvbi0wMQ0K
DQoNCldlIHdvdWxkIGxpa2UgdG8gcG9sbCB0aGUgV0cgdG8gZGVjaWRlIGlmIA0KZHJhZnQtdHNv
dS1tYm9uZWQtbXVsdHJhbnMtYWRkci1hY3F1aXNpdGlvbi0wMSBzaG91bGQgYmUgYWRvcHRlZCBh
cyBhbiANCk1CT05FRCBkb2N1bWVudC4gIFBsZWFzZSByZXNwbmQgYnkgTWF5IDI5IGlmIHlvdSB0
aGluZyB0aGlzIGRvYyBzaG91bGQgb3IgDQpzaG91bGQgbm90IGJlIGFkb3B0ZWQgYnkgTUJPTkVE
Lg0KDQoNCi1NQk9ORUQgQ2hhaXJzDQoNCg0KT24gVGh1LCAxMCBNYXkgMjAxMiwgVGluYSBUU09V
IHdyb3RlOg0KDQotKSBEZWFyIGNoYWlycywNCi0pIFdvdWxkIHlvdSBhc2sgdGhlIFdHIGZvciBh
ZG9wdGlvbiBvZiBkcmFmdC10c291LW1ib25lZC1tdWx0cmFucy1hZGRyLWFjcXVpc2l0aW9uLTAx
IGFzIFdHIGRvY3VtZW50Pw0KLSkgDQotKSBUaGFuayB5b3UgYW5kIGhhdmUgYSBnb29kIGRheS4N
Ci0pIA0KLSkgVGluYSBhbmQgY28tYXV0aG9ycw0KLSkgDQotKSBGcm9tOiBUaW5hIFRTT1UNCi0p
IFNlbnQ6IFdlZG5lc2RheSwgTWF5IDAyLCAyMDEyIDExOjU4IEFNDQotKSBUbzogbWJvbmVkQGll
dGYub3JnDQotKSBTdWJqZWN0OiBkcmFmdC10c291LW1ib25lZC1tdWx0cmFucy1hZGRyLWFjcXVp
c2l0aW9uLTAxDQotKSANCi0pIA0KLSkgTm93IHRoYXQgdGhlIG11bHRpY2FzdCB0cmFuc2l0aW9u
IGZyYW1ld29yayBkb2N1bWVudCBpcyBvZmZpY2lhbGx5IGFjY2VwdGVkLCBpcyB0aGUgV29ya2lu
ZyBHcm91cCBwcmVwYXJlZCBhbHNvIHRvIHRha2Ugb24gdGhlIHRvcGljIG9mIGFkZHJlc3MgYWNx
dWlzaXRpb24sIHdoaWNoIGlzIG9uZSBvZiB0aGUgdGFza3MgaXQgaWRlbnRpZmllcz8NCi0pIElm
IHNvLCB3b3VsZCBkcmFmdC10c291LW1ib25lZC1tdWx0cmFucy1hZGRyLWFjcXVpc2l0aW9uLTAx
IGJlIGFjY2VwdGFibGUgYXMgYSBzdGFydGluZyBwb2ludD8NCi0pIA0KLSkgVGluYQ0KLSkgDQot
KSANCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpNQk9O
RUQgbWFpbGluZyBsaXN0DQpNQk9ORURAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vbWJvbmVk

------=_001_NextPart854745473772_=----
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dgb2312" http-equiv=3DContent-Type>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: =CE=A2=C8=ED=D1=C5=BA=DA; COLOR: #000000; =
FONT-SIZE: 10.5pt
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 8.00.7600.16968"></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV>+1 support</DIV>
<DIV>&nbsp;</DIV>
<DIV>Chongfeng Xie</DIV>
<DIV>&nbsp;</DIV>
<HR style=3D"WIDTH: 210px; HEIGHT: 1px" align=3Dleft color=3D#b5c4df SIZE=
=3D1>

<DIV><SPAN>
<DIV>
<DIV>&nbsp;</DIV>
<DIV>
<DIV>&nbsp;</DIV>
<DIV>-----Original&nbsp;Message-----</DIV>
<DIV>From:&nbsp;mboned-bounces@ietf.org&nbsp;[mailto:mboned-bounces@ietf.o=
rg]&nbsp;On&nbsp;Behalf&nbsp;Of&nbsp;Leonard&nbsp;Giuliano</DIV>
<DIV>Sent:&nbsp;Tuesday,&nbsp;May&nbsp;15,&nbsp;2012&nbsp;4:24&nbsp;AM</DI=
V>
<DIV>To:&nbsp;MBONED&nbsp;WG</DIV>
<DIV>Subject:&nbsp;Re:&nbsp;[MBONED]&nbsp;draft-tsou-mboned-multrans-addr-=
acquisition-01</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>We&nbsp;would&nbsp;like&nbsp;to&nbsp;poll&nbsp;the&nbsp;WG&nbsp;to&nb=
sp;decide&nbsp;if&nbsp;</DIV>
<DIV>draft-tsou-mboned-multrans-addr-acquisition-01&nbsp;should&nbsp;be&nb=
sp;adopted&nbsp;as&nbsp;an&nbsp;</DIV>
<DIV>MBONED&nbsp;document.&nbsp;&nbsp;Please&nbsp;respnd&nbsp;by&nbsp;May&=
nbsp;29&nbsp;if&nbsp;you&nbsp;thing&nbsp;this&nbsp;doc&nbsp;should&nbsp;or=
&nbsp;</DIV>
<DIV>should&nbsp;not&nbsp;be&nbsp;adopted&nbsp;by&nbsp;MBONED.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>-MBONED&nbsp;Chairs</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>On&nbsp;Thu,&nbsp;10&nbsp;May&nbsp;2012,&nbsp;Tina&nbsp;TSOU&nbsp;wro=
te:</DIV>
<DIV>&nbsp;</DIV>
<DIV>-)&nbsp;Dear&nbsp;chairs,</DIV>
<DIV>-)&nbsp;Would&nbsp;you&nbsp;ask&nbsp;the&nbsp;WG&nbsp;for&nbsp;adopti=
on&nbsp;of&nbsp;draft-tsou-mboned-multrans-addr-acquisition-01&nbsp;as&nbs=
p;WG&nbsp;document?</DIV>
<DIV>-)&nbsp;</DIV>
<DIV>-)&nbsp;Thank&nbsp;you&nbsp;and&nbsp;have&nbsp;a&nbsp;good&nbsp;day.<=
/DIV>
<DIV>-)&nbsp;</DIV>
<DIV>-)&nbsp;Tina&nbsp;and&nbsp;co-authors</DIV>
<DIV>-)&nbsp;</DIV>
<DIV>-)&nbsp;From:&nbsp;Tina&nbsp;TSOU</DIV>
<DIV>-)&nbsp;Sent:&nbsp;Wednesday,&nbsp;May&nbsp;02,&nbsp;2012&nbsp;11:58&=
nbsp;AM</DIV>
<DIV>-)&nbsp;To:&nbsp;mboned@ietf.org</DIV>
<DIV>-)&nbsp;Subject:&nbsp;draft-tsou-mboned-multrans-addr-acquisition-01<=
/DIV>
<DIV>-)&nbsp;</DIV>
<DIV>-)&nbsp;</DIV>
<DIV>-)&nbsp;Now&nbsp;that&nbsp;the&nbsp;multicast&nbsp;transition&nbsp;fr=
amework&nbsp;document&nbsp;is&nbsp;officially&nbsp;accepted,&nbsp;is&nbsp;=
the&nbsp;Working&nbsp;Group&nbsp;prepared&nbsp;also&nbsp;to&nbsp;take&nbsp=
;on&nbsp;the&nbsp;topic&nbsp;of&nbsp;address&nbsp;acquisition,&nbsp;which&=
nbsp;is&nbsp;one&nbsp;of&nbsp;the&nbsp;tasks&nbsp;it&nbsp;identifies?</DIV=
>
<DIV>-)&nbsp;If&nbsp;so,&nbsp;would&nbsp;draft-tsou-mboned-multrans-addr-a=
cquisition-01&nbsp;be&nbsp;acceptable&nbsp;as&nbsp;a&nbsp;starting&nbsp;po=
int?</DIV>
<DIV>-)&nbsp;</DIV>
<DIV>-)&nbsp;Tina</DIV>
<DIV>-)&nbsp;</DIV>
<DIV>-)&nbsp;</DIV>
<DIV>_______________________________________________</DIV>
<DIV>MBONED&nbsp;mailing&nbsp;list</DIV>
<DIV>MBONED@ietf.org</DIV>
<DIV>https://www.ietf.org/mailman/listinfo/mboned</DIV></DIV></DIV></SPAN>=
</DIV></BODY></HTML>

------=_001_NextPart854745473772_=------


From iesg-secretary@ietf.org  Tue May 29 09:38:01 2012
Return-Path: <iesg-secretary@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 5B3CF21F86D1; Tue, 29 May 2012 09:38:01 -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 YgtlPcuvqhhv; Tue, 29 May 2012 09:38:00 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C82C21F8720; Tue, 29 May 2012 09:38:00 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120529163800.29739.71820.idtracker@ietfa.amsl.com>
Date: Tue, 29 May 2012 09:38:00 -0700
Cc: mboned mailing list <mboned@ietf.org>, mboned chair <mboned-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [MBONED] Document Action: 'Multicast Addresses for Documentation' to	Informational RFC (draft-ietf-mboned-mcaddrdoc-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: Tue, 29 May 2012 16:38:01 -0000

The IESG has approved the following document:
- 'Multicast Addresses for Documentation'
  (draft-ietf-mboned-mcaddrdoc-04.txt) as Informational RFC

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

The IESG contact persons are Ronald Bonica and Benoit Claise.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-mboned-mcaddrdoc/




    It is often useful in documentation, IETF documents, etc., to provide
    examples containing IP multicast addresses.  For documentation where
    examples of general purpose multicast addresses are needed, one
    should use multicast addresses that never will be assigned or in
    actual use.  There is a risk that addresses used in examples may
    accidentally be used.  It is then important that the same addresses
    are not used by other multicast applications or services.  It may
    also be beneficial to filter out such addresses from multicast
    signalling and multicast data sent to such addresses.

    For unicast there are both IPv4 and IPv6 addresses reserved for this
    purpose, see [RFC5737] and [RFC3849] respectively.  This document
    reserves multicast addresses for this purpose.

    There are also some multicast addresses that are derived from AS
    numbers or unicast addresses.  For examples where such addresses are
    desired, one should derive them from the AS numbers and unicast

    addresses reserved for documentation purposes.  This document also
    discusses the use of these.


Working Group Summary

    This draft has received solid support within the working group and no
    major controversies were noted.

Document Quality

    This document has received several comments from reviewers and the
    authors addressed each of these comments.

Personnel

    Lenny Giuliano is the Document Shepherd. Ron Bonica is the
    Responsible Area Director.


RFC Editor Note

- Please remove unused reference to RFC 3307




From xiaohong.deng@orange.com  Wed May 30 02:27:33 2012
Return-Path: <xiaohong.deng@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 5BBEE21F86D0 for <mboned@ietfa.amsl.com>; Wed, 30 May 2012 02:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level: 
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 nOUU2c14RnCw for <mboned@ietfa.amsl.com>; Wed, 30 May 2012 02:27:32 -0700 (PDT)
Received: from r-mail1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by ietfa.amsl.com (Postfix) with ESMTP id 6E16021F86C9 for <mboned@ietf.org>; Wed, 30 May 2012 02:27:32 -0700 (PDT)
Received: from r-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 46826DE4007 for <mboned@ietf.org>; Wed, 30 May 2012 11:29:03 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail1.rd.francetelecom.com (Postfix) with ESMTP id 0BF56DE4001 for <mboned@ietf.org>; Wed, 30 May 2012 11:29:03 +0200 (CEST)
Received: from ch-mailsrv.rd.francetelecom.fr ([10.193.250.27]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 May 2012 11:27:29 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CD3E46.6D7C790B"
Date: Wed, 30 May 2012 17:27:25 +0800
Message-ID: <0962B0BEF842A24191AD9BE41A8DD2FC0225273A@ch-mailsrv.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
Thread-Index: Ac0+Rmyf4t4RoNu6SOGpMVdBGUuYzQ==
From: <xiaohong.deng@orange.com>
To: <mboned@ietf.org>
X-OriginalArrivalTime: 30 May 2012 09:27:29.0292 (UTC) FILETIME=[6EE7A4C0:01CD3E46]
Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01
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, 30 May 2012 09:27:33 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CD3E46.6D7C790B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I see this is in a good shape to be adopted.

=20

Cheers,

Xiaohong

-----Original Message-----

From: mboned-bounces at ietf.org [mailto:mboned-bounces at ietf.org] On
Behalf Of Leonard Giuliano

Sent: Tuesday, May 15, 2012 4:24 AM

To: MBONED WG

Subject: Re: [MBONED] draft-tsou-mboned-multrans-addr-acquisition-01

=20

We would like to poll the WG to decide if=20

draft-tsou-mboned-multrans-addr-acquisition-01 should be adopted as an=20

MBONED document.  Please respnd by May 29 if you thing this doc should
or=20

should not be adopted by MBONED.

=20

-MBONED Chairs

=20


------_=_NextPart_001_01CD3E46.6D7C790B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:\5B8B\4F53;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@\5B8B\4F53";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DFR link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US>I see this is in a good shape to be =
adopted.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Cheers,<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Xiaohong<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>-----Original Message-----<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>From: mboned-bounces at ietf.org =
[mailto:mboned-bounces at ietf.org] On Behalf Of Leonard =
Giuliano<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Sent: Tuesday, May 15, 2012 4:24 AM<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>To: MBONED =
WG<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>Subject: =
Re: [MBONED] =
draft-tsou-mboned-multrans-addr-acquisition-01<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US> <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>We would like to poll the WG to =
decide if <o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>draft-tsou-mboned-multrans-addr-acquisition-01 should be =
adopted as an <o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>MBONED document.&nbsp; Please respnd by May 29 if you thing =
this doc should or <o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>should not be adopted by MBONED.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US> <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal>-MBONED Chairs<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------_=_NextPart_001_01CD3E46.6D7C790B--

From kurtw@juniper.net  Wed May 30 17:36:09 2012
Return-Path: <kurtw@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 C304C11E811A for <mboned@ietfa.amsl.com>; Wed, 30 May 2012 17:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 pgvfgwHmmAXg for <mboned@ietfa.amsl.com>; Wed, 30 May 2012 17:36:09 -0700 (PDT)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id E37FC11E80D5 for <mboned@ietf.org>; Wed, 30 May 2012 17:36:08 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKT8a89k7LPqSzYL8dNn5Lx3+WRtP09j34@postini.com; Wed, 30 May 2012 17:36:08 PDT
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Wed, 30 May 2012 17:34:52 -0700
From: Kurt Windisch <kurtw@juniper.net>
To: "gjshep@gmail.com" <gjshep@gmail.com>, "mboned@ietf.org" <mboned@ietf.org>
Date: Wed, 30 May 2012 17:35:19 -0700
Thread-Topic: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
Thread-Index: Ac0u0v6BqadEAQZyTMGV0mw+Ga8SlgPC5fxA
Message-ID: <189716C74BBB9C4095FE8CA503B1FC3A59241537C0@EMBX02-HQ.jnpr.net>
References: <CABFReBqo43QsBWwu=_nbDgw-eoK1S2+8xszTXY1Zm=KLhmvRPA@mail.gmail.com>
In-Reply-To: <CABFReBqo43QsBWwu=_nbDgw-eoK1S2+8xszTXY1Zm=KLhmvRPA@mail.gmail.com>
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: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
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, 31 May 2012 00:36:09 -0000

Sorry for the 11th-hour response to this WGLC.

I do have a couple of comments:

1. The IGMPv3 spec calls for the type-of-service bit for IP control to be s=
et on all IGMP packets (section 4 of RFC 3376, "Every IGMP message describe=
d in this document is sent with ... IP Precedence of Internetwork Control (=
e.g., Type of Service 0xc0) ...". It seems logical that IPv4 AMT control me=
ssages should have the same TOS as the control packets that they encapsulat=
e. Thus, I'd like to suggest that all IPv4 AMT control packets (AMT packets=
 EXCEPT the AMT Data packet) should have TOS 0xc0.=20

2. (nit) In the new text of section 5.2.3.5.4, it states: The IGMP and MLD =
protocol specifications indicate that senders should use a link-local sourc=
e IP address in message datagrams." This is incorrect since it is only appl=
ies to MLD and only the MLD specs make such a statement.

I don't see any problems with the rest of the document or changes.

Thanks
--Kurt

-----Original Message-----
From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf Of=
 Greg Shepherd
Sent: Thursday, May 10, 2012 10:33 AM
To: mboned@ietf.org
Subject: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13

*,

Yes, I think we may finally be here! The Paris and post-Paris
discussions were addressed in the finally rev so it is now time for
WGLC for draft-ietf-mboned-auto-multicast-13:

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

It is quite long so we'll give it three weeks for responses before
moving it along. Please respond by May 31st. And as always, we need
votes of approval as much as comments and issues. Let's see this
finally move to req pub!

Thanks to everyone who has been involved throughout the past +decade. :p

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

From tom.taylor.stds@gmail.com  Wed May 30 20:15:41 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 D726F11E80FA for <mboned@ietfa.amsl.com>; Wed, 30 May 2012 20:15:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.849
X-Spam-Level: 
X-Spam-Status: No, score=-3.849 tagged_above=-999 required=5 tests=[AWL=-0.250, 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 etSBY8sqsDFl for <mboned@ietfa.amsl.com>; Wed, 30 May 2012 20:15:41 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id DC83E11E8093 for <mboned@ietf.org>; Wed, 30 May 2012 20:15:40 -0700 (PDT)
Received: by lagv3 with SMTP id v3so392527lag.31 for <mboned@ietf.org>; Wed, 30 May 2012 20:15:39 -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 :content-type:content-transfer-encoding:x-antivirus :x-antivirus-status; bh=fwNKL3OGfxgK0IRUkKjOXucuG8CHDgmdd0Xfn7U0jx0=; b=qEYtZ04hOaRVLb+eSgjQk+eOMvKd2Sxqkj3bEJ/FxTy34q4ft5LJQdXgSkvIwPt8lO n2BX6WL/FNzb3ZtqiV6LYh22Y1i40Coi8CgvxgnZt8r0VcVYHYOipPLFvY9ZlfVyXSTG CzUPHCkWZfmPVcINWTR6MuF0ww5W6MQOYc8JfGMthD47c3UQtvmRl5yrPzpBjL7WGige 9UGzn3780+mLvaK5iFPeFCMXSKtgmGrmtVb6+gp9gWC+N5rN90sriXW+f5RgQKV0iKcW yzPrithVJkdRTrTKiFQH7W2oStFRMrNKCbnc4GwjOzehKfczT7HeGhROaZTWgTpLFwLQ jjPA==
Received: by 10.112.24.197 with SMTP id w5mr227947lbf.11.1338434139775; Wed, 30 May 2012 20:15:39 -0700 (PDT)
Received: from [127.0.0.1] (dsl-207-112-91-137.tor.primus.ca. [207.112.91.137]) by mx.google.com with ESMTPS id gd9sm1283695lbb.15.2012.05.30.20.15.36 (version=SSLv3 cipher=OTHER); Wed, 30 May 2012 20:15:37 -0700 (PDT)
Message-ID: <4FC6E255.7040500@gmail.com>
Date: Wed, 30 May 2012 23:15:33 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: MBONED WG <mboned@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 120530-2, 30/05/2012), Outbound message
X-Antivirus-Status: Clean
Subject: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
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, 31 May 2012 03:15:42 -0000

I have reviewed the document and found it good to go. One substantive 
query: the last paragraph of section 5.3.3.2 says:

   "If the Relay Discovery message was
    received as an IPv6 datagram, the relay may return an IPv4 or IPv6
    address in the Relay Address field."

This seems to impose a requirement that any Gateway supporting IPv6 
transport MUST also support IPv4. Is that the intention?

Nits:

4.2.2.1 second para, first sentence: s/change/changes/ to agree with 
"address".

5.1.5 typos:

- second para, first line: s/a receives/it receives/

- third para end of third line: s/Message/Membership/ (Update message)

5.2.1 third para, third-last line: s/primary/primarily/

5.2.2.1 and 5.2.2.2: Don't these appear in reverse order of usage? I'd 
suggest taking the word "Static" out of the sub-section titles and 
reversing their order.

5.2.3.6.1 final paragraph seems out of place -- it refers to "the 
datagram", where that is not present in the immediately preceding text. 
I suggest moving the final paragraph up to precede the paragraph 
beginning: "A gateway that waits to start ...".

5.3.1 fourth para, first line: s/,Section/in Section/

5.3.2: Should the second paragraph specify that the assigned addresses 
are globally reachable?

5.3.3.3:
- eighth para (third down on p. 64), tenth line: missing text. That line 
and the one following currently read:

"This exception is made because any address that a relay might may not
                                                             ^^^^^
  be a valid source address on any gateway interface.  The rationale ..."

- second-last para, last sentence (top of p. 65):
         s/a membership/membership/

5.3.3.4, third-last para: missing "of" between "form" and "group".

5.3.3.6 first para, last line: s/follow/following/

5.3.3.8 last para, second line: s/reach/reached/

7.1.1 second para: missing space

I didn't check the Appendix.

Tom Taylor

From gbumgard@cisco.com  Wed May 30 22:34:53 2012
Return-Path: <gbumgard@cisco.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 44A0211E809A for <mboned@ietfa.amsl.com>; Wed, 30 May 2012 22:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 FwgviHWKzy9O for <mboned@ietfa.amsl.com>; Wed, 30 May 2012 22:34:52 -0700 (PDT)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com [72.163.197.26]) by ietfa.amsl.com (Postfix) with ESMTP id E464321F862B for <mboned@ietf.org>; Wed, 30 May 2012 22:34:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=gbumgard@cisco.com; l=2424; q=dns/txt; s=iport; t=1338442492; x=1339652092; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=/uTkLvD2teWkRPF8o5ryBoCLHeDqP/aQeiLNwObZqlk=; b=bceFPzqEIhdAM0JU9f6Qd5+HGOhWAcdbMa61p4RahniANfVa3uydx2Dr xc79zSxayLNyg3vBkqedbPK9XSSaV253Ah4/BANrFAhEAAnzRnZRTo9WR i970nyHY1jAVY1Z6e3dYK/Mr+O0//Y1vSrmrWHyavSdCDhk9uqbRgN6lG c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuUEAA8Cx09Io8UY/2dsb2JhbABEgx2xfoIXAQEBBAEBAQ8BJTYKEQsYCRYPCQMCAQIBFTATBgIBAR6HaQuZGZ9rBIsIgjCDFgOIQIxYhU+IPoFmgwA
X-IronPort-AV: E=Sophos;i="4.75,688,1330905600"; d="scan'208";a="13587541"
Received: from vla196-nat.cisco.com (HELO bgl-core-2.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 31 May 2012 05:34:50 +0000
Received: from [10.20.185.146] (sjc-gbumgard-8911.cisco.com [10.20.185.146]) by bgl-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q4V5Ymml013843 for <mboned@ietf.org>; Thu, 31 May 2012 05:34:49 GMT
Message-ID: <4FC702DE.5050701@cisco.com>
Date: Wed, 30 May 2012 22:34:22 -0700
From: Greg Bumgardner <gbumgard@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: mboned@ietf.org
References: <4FC6E255.7040500@gmail.com>
In-Reply-To: <4FC6E255.7040500@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
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, 31 May 2012 05:34:53 -0000

  Thanks Tom,

One comment below...

-g.b.

On 5/30/2012 8:15 PM, Tom Taylor wrote:
> I have reviewed the document and found it good to go. One substantive 
> query: the last paragraph of section 5.3.3.2 says:
>
>   "If the Relay Discovery message was
>    received as an IPv6 datagram, the relay may return an IPv4 or IPv6
>    address in the Relay Address field."
>
> This seems to impose a requirement that any Gateway supporting IPv6 
> transport MUST also support IPv4. Is that the intention?
>
I had intended to remove that statement but must have missed it. I 
believe we cannot impose that requirement.
> Nits:
>
> 4.2.2.1 second para, first sentence: s/change/changes/ to agree with 
> "address".
>
> 5.1.5 typos:
>
> - second para, first line: s/a receives/it receives/
>
> - third para end of third line: s/Message/Membership/ (Update message)
>
> 5.2.1 third para, third-last line: s/primary/primarily/
>
> 5.2.2.1 and 5.2.2.2: Don't these appear in reverse order of usage? I'd 
> suggest taking the word "Static" out of the sub-section titles and 
> reversing their order.
>
> 5.2.3.6.1 final paragraph seems out of place -- it refers to "the 
> datagram", where that is not present in the immediately preceding 
> text. I suggest moving the final paragraph up to precede the paragraph 
> beginning: "A gateway that waits to start ...".
>
> 5.3.1 fourth para, first line: s/,Section/in Section/
>
> 5.3.2: Should the second paragraph specify that the assigned addresses 
> are globally reachable?
>
> 5.3.3.3:
> - eighth para (third down on p. 64), tenth line: missing text. That 
> line and the one following currently read:
>
> "This exception is made because any address that a relay might may not
>                                                             ^^^^^
>  be a valid source address on any gateway interface.  The rationale ..."
>
> - second-last para, last sentence (top of p. 65):
>         s/a membership/membership/
>
> 5.3.3.4, third-last para: missing "of" between "form" and "group".
>
> 5.3.3.6 first para, last line: s/follow/following/
>
> 5.3.3.8 last para, second line: s/reach/reached/
>
> 7.1.1 second para: missing space
>
> I didn't check the Appendix.
>
> Tom Taylor
> _______________________________________________
> MBONED mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
>


From rs1983@att.com  Thu May 31 09:46:23 2012
Return-Path: <rs1983@att.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 E57A311E8138 for <mboned@ietfa.amsl.com>; Thu, 31 May 2012 09:46:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.599
X-Spam-Level: 
X-Spam-Status: No, score=-105.599 tagged_above=-999 required=5 tests=[AWL=1.000, 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 tcAFHPmmuEAY for <mboned@ietfa.amsl.com>; Thu, 31 May 2012 09:46:23 -0700 (PDT)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) by ietfa.amsl.com (Postfix) with ESMTP id D864C11E80F4 for <mboned@ietf.org>; Thu, 31 May 2012 09:46:22 -0700 (PDT)
Received: from unknown [144.160.20.146] (EHLO nbfkord-smmo06.seg.att.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.11.0-10) with ESMTP id e50a7cf4.2aaaccc0d940.172178.00-592.473998.nbfkord-smmo06.seg.att.com (envelope-from <rs1983@att.com>);  Thu, 31 May 2012 16:46:22 +0000 (UTC)
X-MXL-Hash: 4fc7a05e4c8242a2-9c3204923947da57a96d4e3d5c4cb0f8d0d26d17
Received: from unknown [144.160.20.146] (EHLO mlpd194.enaf.sfdc.sbc.com) by nbfkord-smmo06.seg.att.com(mxl_mta-6.11.0-10) over TLS secured channel with ESMTP id 350a7cf4.0.172093.00-370.473745.nbfkord-smmo06.seg.att.com (envelope-from <rs1983@att.com>);  Thu, 31 May 2012 16:46:12 +0000 (UTC)
X-MXL-Hash: 4fc7a0540fb682ea-0da00075259c84f7e26ab99325b5c236e46cbb87
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q4VGkApo028647; Thu, 31 May 2012 12:46:11 -0400
Received: from sflint03.pst.cso.att.com (sflint03.pst.cso.att.com [144.154.234.230]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q4VGk4xt028531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 31 May 2012 12:46:05 -0400
Received: from GAALPA1MSGHUB9D.ITServices.sbc.com (gaalpa1msghub9d.itservices.sbc.com [130.8.36.90]) by sflint03.pst.cso.att.com (RSA Interceptor); Thu, 31 May 2012 12:45:43 -0400
Received: from GAALPA1MSGUSR9N.ITServices.sbc.com ([130.8.36.71]) by GAALPA1MSGHUB9D.ITServices.sbc.com ([130.8.36.90]) with mapi id 14.01.0355.002; Thu, 31 May 2012 12:45:43 -0400
From: "SAYKO, ROBERT J" <rs1983@att.com>
To: "gjshep@gmail.com" <gjshep@gmail.com>, "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
Thread-Index: AQHNLtMBgiJFuOJXlECYyfyNOZHbHpbU9eEAgA9FvYA=
Date: Thu, 31 May 2012 16:45:42 +0000
Message-ID: <9B30768B8155174FB7C6B21ABDCD24C001DC5DA8@GAALPA1MSGUSR9N.ITServices.sbc.com>
References: <CABFReBqo43QsBWwu=_nbDgw-eoK1S2+8xszTXY1Zm=KLhmvRPA@mail.gmail.com> <CABFReBof8GKz=yzmPxLGk+eTsUE20PYvZOyO9fqMcY8oFcwnow@mail.gmail.com>
In-Reply-To: <CABFReBof8GKz=yzmPxLGk+eTsUE20PYvZOyO9fqMcY8oFcwnow@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.194.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <rs1983@att.com>
X-SOURCE-IP: [144.160.20.146]
X-AnalysisOut: [v=1.0 c=1 a=_lUgunBsMlQA:10 a=HemsPGZEDp8A:10 a=ofMgfj31e3]
X-AnalysisOut: [cA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:10 a=Qs8R1XBwmid1qB]
X-AnalysisOut: [FB/a8mmA==:17 a=48vgC7mUAAAA:8 a=pGLkceISAAAA:8 a=p2DRDVHB]
X-AnalysisOut: [u2pO3pkIgZEA:9 a=wPNLvfGTeEIA:10 a=lZB815dzVvQA:10 a=MSl-t]
X-AnalysisOut: [DqOz04A:10 a=1Jv4V1FR3LQV51MU:21 a=5AGxuKGt3CIxO4Vv:21]
Cc: Greg Shepherd <shep@cisco.com>
Subject: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13
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, 31 May 2012 16:46:24 -0000

Greg, et al,


Here are our comments.


A) Our expectation is that multicast datagrams may be fragmented and contai=
ned in more than one AMT Data message.   The document seems pretty consiste=
nt that an AMT Multicast data message contains the entire IP multicast data=
gram is there a disconnect here?

There are several places where this should be addressed:

Section 4.2.1 "Multicast Data:  Sent by relays to deliver an encapsulated I=
P multicast datagram to a gateway"  =E0 ".. to deliver an encapsulated IP m=
ulticast datagram (or fragment thereof) to a gateway."
Section 4.2.2.3 "each multicast IP datagram that arrives at the relay is en=
capsulated in an AMT message" =E0 "encapsulated in one or more AMT message"
Section 5.1.6 "A relay sends a Multicast Data message to deliver an IP mult=
icast packet" =E0 "sends one or more Multicast Data messages."
Section 5.1.6.4 "A complete IPv4 or IPv6 Multicast datagram" =E0 "A complet=
e or fragment of an IPv4 ."



B) Would like to recommend the following text from section "5.3.3.2. Handli=
ng a Relay Discovery Message":

	If the Relay Discovery message was received as an IPv4 datagram, the
   	relay MUST return an IPv4 address in the Relay Address field of the
   	Relay Advertisement message.  If the Relay Discovery message was
   	received as an IPv6 datagram, the relay may return an IPv4 or IPv6
   	address in the Relay Address field.

included in section "5.1.2.5 Relay Address" as well. =20


C) Would like to recommend some clarification regarding the "Response MAC" =
in the Teardown message.  Section "5.1.7.4. Response MAC" states:=20

   	A 48-bit value copied from the Response MAC field (Section 5.1.4.6)
   	in the last Membership Query message the relay sent to the gateway
   	endpoint address of the tunnel to be torn down.  The gateway endpoint
   	address is provided by the Gateway IP Address and Gateway Port Number
   	fields carried by the Membership Query message.

We believe this implies that the Relay will need to keep track of the last =
"Response MAC" sent to the Gateway. =20

If this is the intention, then section "4.2.1.3. Teardown Sequence" bullet =
"8" and section "5.3.3.5. Handling a Teardown Message" should be updated ac=
cordingly. =20

If this is not the intention, then section "5.1.7.4. Response MAC" should b=
e reworded. =20


Regards,
Bob Sayko and the AT&T AMT team.

-----Original Message-----
From: mboned-bounces@ietf.org [mailto:mboned-bounces@ietf.org] On Behalf Of=
 Greg Shepherd
Sent: Monday, May 21, 2012 3:31 PM
To: mboned@ietf.org
Subject: Re: [MBONED] WGLC draft-ietf-mboned-auto-multicast-13

We're half way through the 3 week WGLC for AMT and we've received no
responses. Please read and respond ASAP so we can progress.

Thanks,
Greg

On Thu, May 10, 2012 at 10:33 AM, Greg Shepherd <gjshep@gmail.com> wrote:
> *,
>
> Yes, I think we may finally be here! The Paris and post-Paris
> discussions were addressed in the finally rev so it is now time for
> WGLC for draft-ietf-mboned-auto-multicast-13:
>
> https://datatracker.ietf.org/doc/draft-ietf-mboned-auto-multicast/
>
> It is quite long so we'll give it three weeks for responses before
> moving it along. Please respond by May 31st. And as always, we need
> votes of approval as much as comments and issues. Let's see this
> finally move to req pub!
>
> Thanks to everyone who has been involved throughout the past +decade. :p
>
> MBONED Chairs
_______________________________________________
MBONED mailing list
MBONED@ietf.org
https://www.ietf.org/mailman/listinfo/mboned
