Re: MLDv1/v2
"Beeram, Suresh KumarReddy" <[email protected]> Mon, 25 Apr 2011 03:50:14 +0000
| Newsgroups | gmane.ietf.magma |
|---|---|
| Message-ID | <23E658492CE48649B5B5168EBC60387842D140C01F@GVW1101EXC.americas.hpqcorp.net> |
--===============0333821195923134153==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_23E658492CE48649B5B5168EBC60387842D140C01FGVW1101EXCame_"
--_000_23E658492CE48649B5B5168EBC60387842D140C01FGVW1101EXCame_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi Rekha,
When we are in version2 we need to send initial reports TO_EX(Multicast ad=
dress,{null}), [RV] times, [URI] seconds apart.
When we are version1 we need to send MLDV1 report for multicast address [RV=
] times, [URI] seconds apart .
I didn't find any IETF doc which explains in detail..but I found for MLDV2 =
in TAHI conformance test suite,
So same applies for MLDV1.
Refer testcase-1.
http://www.ipv6ready.org/docs/Phase2_MLDv2_Router_Conformance_Latest.pdf
Thanks
-B S Reddy
From: [email protected] [mailto:[email protected]] On Behalf Of R=
ekha Mundhra
Sent: Saturday, April 23, 2011 3:53 AM
To: [email protected]
Subject: [magma] MLDv1/v2
Hi All,
Had a question regarding the MLD router behavior when MLD is enabled on an =
interface with reference to
Neighbor Discovery RFC 4861 attached below for reference:
******* RFC 4861 ************
7.2.1. Interface Initialization
When a multicast-capable interface becomes enabled, the node MUST
join the all-nodes multicast address on that interface, as well as
the solicited-node multicast address corresponding to each of the IP
addresses assigned to the interface.
The set of addresses assigned to an interface may change over time.
New addresses might be added and old addresses might be removed
[ADDRCONF]. In such cases the node MUST join and leave the
solicited-node multicast address corresponding to the new and old
addresses, respectively. Joining the solicited-node multicast
address is done using a Multicast Listener Discovery such as [MLD] or
[MLDv2] protocols. Note that multiple unicast addresses may map into
the same solicited-node multicast address; a node MUST NOT leave the
solicited-node multicast group until all assigned addresses
corresponding to that multicast address have been removed.
***********
What are the MLD join packets that should be sent when the interface has ve=
rsion
MLDv1 and when the version is MLDv2. Is there some IETF document
that provides more details on this behavior. Have not found any clear descr=
iption
in RFCs 3810 or 2710.
regards,
-rekha
--_000_23E658492CE48649B5B5168EBC60387842D140C01FGVW1101EXCame_
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:"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:Times;
panose-1:2 2 6 3 5 4 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
p.SectionTitle3, li.SectionTitle3, div.SectionTitle3
{mso-style-name:"Section Title 3";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:4.0pt;
margin-left:.25in;
text-indent:-.25in;
page-break-after:avoid;
mso-list:l0 level1 lfo1;
font-size:12.0pt;
font-family:"Times","serif";
color:black;
font-weight:bold;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:2107340994;
mso-list-template-ids:-397654394;}
@list l0:level1
{mso-level-style-link:"Section Title 3";
mso-level-tab-stop:.25in;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;}
@list l0:level2
{mso-level-suffix:space;
mso-level-text:"%2\.%1\.";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;}
@list l0:level3
{mso-level-text:"%1\.%2\.%3\.";
mso-level-tab-stop:.5in;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;}
@list l0:level4
{mso-level-text:"%1\.%2\.%3\.%4\.";
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
margin-left:1.2in;
text-indent:-.45in;}
@list l0:level5
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.";
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
margin-left:1.55in;
text-indent:-.55in;}
@list l0:level6
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.";
mso-level-tab-stop:2.25in;
mso-level-number-position:left;
margin-left:1.9in;
text-indent:-.65in;}
@list l0:level7
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.";
mso-level-tab-stop:2.75in;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.75in;}
@list l0:level8
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.";
mso-level-tab-stop:3.25in;
mso-level-number-position:left;
margin-left:2.6in;
text-indent:-.85in;}
@list l0:level9
{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9\.";
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
margin-left:3.0in;
text-indent:-1.0in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Rekha,=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;=
font-family:"Calibri","sans-serif";color:#1F497D'>When we are in version2 w=
e need to send initial reports TO_EX(Multicast address,{null}), [RV] =
times, [URI] seconds apart.<o:p></o:p></span></p><p class=3DMsoNormal><span=
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'>When we are version1 we need to send MLDV1 report for multicast address [=
RV] times, [URI] seconds apart . <o:p></o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'><o:p> </o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I didn̵=
7;t find any IETF doc which explains in detail..but I found for MLDV2  =
;in TAHI conformance test suite,<o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1=
F497D'>So same applies for MLDV1.<o:p></o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'>Refer testcase-1.<o:p></o:p></span></p><p class=3DSectionTitle3 sty=
le=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:4.0pt;margin-le=
ft:0in;text-indent:0in;mso-list:none'><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif";font-weight:normal'><a href=3D"http://www.ipv=
6ready.org/docs/Phase2_MLDv2_Router_Conformance_Latest.pdf">http://www.ipv6=
ready.org/docs/Phase2_MLDv2_Router_Conformance_Latest.pdf</a><o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"C=
alibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=3D=
MsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif=
";color:#1F497D'>Thanks<o:p></o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-B=
S Reddy<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p>=
</span></p><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-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-siz=
e:10.0pt;font-family:"Tahoma","sans-serif"'> [email protected] [mailto=
:[email protected]] <b>On Behalf Of </b>Rekha Mundhra<br><b>Sent:</b> =
Saturday, April 23, 2011 3:53 AM<br><b>To:</b> [email protected]<br><b>Subject=
:</b> [magma] MLDv1/v2<o:p></o:p></span></p></div><p class=3DMsoNormal><o:p=
> </o:p></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-=
family:"Arial","sans-serif"'>Hi All,</span> <br><br><span style=3D'font-siz=
e:10.0pt;font-family:"Arial","sans-serif"'>Had a question regarding the MLD=
router behavior when MLD is enabled on an interface with reference to </sp=
an><br><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Ne=
ighbor Discovery RFC 4861 attached below for reference:</span> <br><br><spa=
n style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>******* RFC 4=
861 ************</span> <o:p></o:p></p><table class=3DMsoNormalTable border=
=3D0 cellspacing=3D3 cellpadding=3D0 width=3D"100%" style=3D'width:100.0%'>=
<tr><td width=3D"100%" valign=3Dtop style=3D'width:100.0%;padding:.75pt .75=
pt .75pt .75pt'><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><tt><i>=
<span style=3D'font-size:10.0pt'>7.2.1. Interface Initialization</spa=
n></i></tt><i><span style=3D'font-size:10.0pt;font-family:"Courier New"'><b=
r><br><tt> When a multicast-capable interface becomes enabled, the no=
de MUST</tt><br><tt> join the all-nodes multicast address on that int=
erface, as well as</tt><br><tt> the solicited-node multicast address =
corresponding to each of the IP</tt><br><tt> addresses assigned to th=
e interface.</tt><br><br><tt> The set of addresses assigned to an int=
erface may change over time.</tt><br><tt> New addresses might be adde=
d and old addresses might be removed</tt><br><tt> [ADDRCONF]. I=
n such cases the node MUST join and leave the</tt><br><tt> solicited-=
node multicast address corresponding to the new and old</tt><br><tt> =
addresses, respectively. Joining the solicited-node multicast</tt><br=
><tt> address is done using a Multicast Listener Discovery such as [M=
LD] or</tt><br><tt> [MLDv2] protocols. Note that multiple unica=
st addresses may map into</tt><br><tt> the same solicited-node multic=
ast address; a node MUST NOT leave the</tt><br><tt> solicited-node mu=
lticast group until all assigned addresses</tt><br><tt> corresponding=
to that multicast address have been removed.</tt></span></i> <br><tt>*****=
******</tt> <br><tt>What are the MLD join packets that should be sent when =
the interface has version </tt><br><tt>MLDv1 and when the version is MLDv2.=
Is there some IETF document </tt> <br><tt>that provides more details=
on this behavior. Have not found any clear description</tt> <br><tt>in RFC=
s 3810 or 2710. </tt><br><br><tt>regards,</tt> <br><tt>-rekha</tt><o:p></o:=
p></p></td></tr></table><p class=3DMsoNormal><o:p> </o:p></p></div></b=
ody></html>=
--_000_23E658492CE48649B5B5168EBC60387842D140C01FGVW1101EXCame_--
--===============0333821195923134153==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
magma mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/magma
--===============0333821195923134153==--