[prev in list] [next in list] [prev in thread] [next in thread]
List: ipng
Subject: RE: [rfc2462bis #596] definition of "multicast-capable"
From: "Elwyn Davies" <elwynd () nortelnetworks ! com>
Date: 2004-08-23 22:29:10
Message-ID: 8F20221FB47FD51190AD00508BCF36BA087D6A4D () znsgy0k3 ! europe ! nortel ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Unfortunately the links are not specified - 2461 says ND applies to all
links unless the link specific doc says otherwise (see the Intro to
2461/2461bis).
So I suggest in place of..
The links on which the protocol used in this document are specified in
[RFC2461].
use..
This protocol will be used on all types of links unless specified otherwise
in the link type specific document describing how to operate IP(v6) on the
link in line with [RFC2461/2461bis].
I am hoping that the definition of multicast-capable will be refined in
2461bis and it should then be referenced in 2462bis.
Regards,
Elwyn
> -----Original Message-----
> From: jinmei@isl.rdc.toshiba.co.jp
> [mailto:jinmei@isl.rdc.toshiba.co.jp]
> Sent: 20 August 2004 16:37
> To: ipv6@ietf.org
> Subject: [rfc2462bis #596] definition of "multicast-capable"
>
>
> (I tried to send this through the issue tracker, but it appears to
> have failed...)
>
> Proposed resolution:
>
> - replace "multicast interface" with "multicast-capable interface" in
> Section 5.1
> - modify the definition of "link" in Section 2 a little bit like:
>
> link - a communication facility or medium over which nodes can
> communicate at the link layer, i.e., the layer immediately below
> IP. Examples are Ethernets (simple or bridged); PPP links; X.25,
> Frame Relay, or ATM networks; and internet (or higher) layer
> "tunnels", such as tunnels over IPv4 or IPv6 itself. The links
> on which the protocol used in this document are specified in
> [RFC2461].
>
> (or s/[RFC2461]/[rfc2461bis]/ if and when necessary)
>
> See the following link for more details:
> http://www1.ietf.org/mail-archive/web/ipv6/current/msg03384.html
>
> I'm going to close this issue with the proposed resolution.
> If anyone of you have an objection, please speak up ASAP.
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
[Attachment #5 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2656.31">
<TITLE>RE: [rfc2462bis #596] definition of "multicast-capable"</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Unfortunately the links are not specified - 2461 says ND applies to \
all links unless the link specific doc says otherwise (see the Intro to \
2461/2461bis).</FONT></P>
<P><FONT SIZE=2>So I suggest in place of..</FONT>
<BR><FONT SIZE=2>The links on which the protocol used in this document are specified \
in [RFC2461].</FONT> </P>
<P><FONT SIZE=2>use..</FONT>
<BR><FONT SIZE=2>This protocol will be used on all types of links unless specified \
otherwise in the link type specific document describing how to operate IP(v6) on the \
link in line with [RFC2461/2461bis].</FONT></P>
<P><FONT SIZE=2>I am hoping that the definition of multicast-capable will be refined \
in 2461bis and it should then be referenced in 2462bis.</FONT></P>
<P><FONT SIZE=2>Regards,</FONT>
<BR><FONT SIZE=2>Elwyn</FONT>
<BR><FONT SIZE=2>> -----Original Message-----</FONT>
<BR><FONT SIZE=2>> From: jinmei@isl.rdc.toshiba.co.jp </FONT>
<BR><FONT SIZE=2>> [<A \
HREF="mailto:jinmei@isl.rdc.toshiba.co.jp">mailto:jinmei@isl.rdc.toshiba.co.jp</A>] \
</FONT> <BR><FONT SIZE=2>> Sent: 20 August 2004 16:37</FONT>
<BR><FONT SIZE=2>> To: ipv6@ietf.org</FONT>
<BR><FONT SIZE=2>> Subject: [rfc2462bis #596] definition of \
"multicast-capable"</FONT> <BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> (I tried to send this through the issue tracker, but it appears \
to</FONT> <BR><FONT SIZE=2>> have failed...)</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Proposed resolution:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> - replace "multicast interface" with \
"multicast-capable interface" in</FONT> <BR><FONT SIZE=2>> \
Section 5.1</FONT> <BR><FONT SIZE=2>> - modify the definition of "link" \
in Section 2 a little bit like:</FONT> <BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> link - a communication facility or medium over which nodes \
can</FONT> <BR><FONT SIZE=2>> communicate at the link layer, i.e., the \
layer immediately below</FONT> <BR><FONT SIZE=2>> IP. Examples are \
Ethernets (simple or bridged); PPP links; X.25,</FONT> <BR><FONT \
SIZE=2>> Frame Relay, or ATM networks; and internet (or higher) \
layer</FONT> <BR><FONT SIZE=2>> "tunnels", such as tunnels \
over IPv4 or IPv6 itself. The links</FONT> <BR><FONT SIZE=2>> on which \
the protocol used in this document are specified in</FONT> <BR><FONT \
SIZE=2>> [RFC2461].</FONT> <BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> (or s/[RFC2461]/[rfc2461bis]/ if and when necessary)</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> See the following link for more details:</FONT>
<BR><FONT SIZE=2>> <A \
HREF="http://www1.ietf.org/mail-archive/web/ipv6/current/msg03384.html" \
TARGET="_blank">http://www1.ietf.org/mail-archive/web/ipv6/current/msg03384.html</A></FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I'm going to close this issue with the proposed \
resolution.</FONT> <BR><FONT SIZE=2>> If anyone of you have an objection, please \
speak up ASAP.</FONT> <BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> \
--------------------------------------------------------------------</FONT> <BR><FONT \
SIZE=2>> IETF IPv6 working group mailing list</FONT> <BR><FONT SIZE=2>> \
ipv6@ietf.org</FONT> <BR><FONT SIZE=2>> Administrative Requests: <A \
HREF="https://www1.ietf.org/mailman/listinfo/ipv6" \
TARGET="_blank">https://www1.ietf.org/mailman/listinfo/ipv6</A></FONT> <BR><FONT \
SIZE=2>> --------------------------------------------------------------------</FONT>
<BR><FONT SIZE=2>> </FONT>
</P>
</BODY>
</HTML>
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic