Re: AW: I-D Action:draft-gundavelli-v6ops-l2-unicast-00.txt

Sri Gundavelli <sgundave@cisco.com> Sun, 25 July 2010 22:55 UTC

User-Agent: Microsoft-Entourage/12.25.0.100505
Date: Sun, 25 Jul 2010 15:53:50 -0700
Subject: Re: AW: I-D Action:draft-gundavelli-v6ops-l2-unicast-00.txt
From: Sri Gundavelli <sgundave@cisco.com>
To: Olaf.Bonness@telekom.de, v6ops@ops.ietf.org
CC: stig@venaas.com
Message-ID: <C8720E8E.46999%sgundave@cisco.com>
Thread-Topic: AW: I-D Action:draft-gundavelli-v6ops-l2-unicast-00.txt
Thread-Index: AcsmFFxNk6Ntts6ipk+C17/0b0cd/gDhPx/QAKy5m6A=
In-Reply-To: <D83105B2AC38794CB78ADA2959F2C44F04613523@S4DE9JSAACY.ost.t-com.de>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

Hi Olaf,

Thanks for the review comments and on the use-case. Its not WG doc yet, but
since its just a clarification note, I'm hoping this can be moved faster.

Regards
Sri
 




On 7/22/10 5:35 AM, "Olaf.Bonness@telekom.de" <Olaf.Bonness@telekom.de>
wrote:

> Hi Sri,
> 
> had a read of your I-D right now and think that it is a very interesting and
> useful work. I see also some applicability in the BBF context for handling of
> RAs in a N:1 VLAN scenario for instance.
> Unfortunately I don't recall the status of the I-D after the last IETF, is it
> on the road to become a WG item?
> I would vote for that.
> Kind regards
> Olaf 
> 
> 
>> -----Ursprüngliche Nachricht-----
>> Von: owner-v6ops@ops.ietf.org
>> [mailto:owner-v6ops@ops.ietf.org] Im Auftrag von Sri Gundavelli
>> Gesendet: Sonntag, 18. Juli 2010 02:59
>> An: IPv6 Operations
>> Cc: Stig Venaas
>> Betreff: Re: AW: I-D Action:draft-gundavelli-v6ops-l2-unicast-00.txt
>> 
>> Thanks to Stig for his review of the draft. Will reword the
>> below text,
>> should be in -01 version.
>> 
>> Sri
>> 
>> 
>> 
>> 
>> ------ Forwarded Message
>> From: Stig Venaas <stig@venaas.com>
>> Date: Mon, 15 Feb 2010 13:03:29 -0800
>> To: Sri Gundavelli <sgundave@cisco.com>
>> Subject: Re: L2 Unicast of multicast messages - ID
>> 
>>>> I think the document is fine. I've followed some of the previous
>>>> discussion on this topic. Just one comment.
>>>> 
>>>> In section 3 it says:
>>>> 
>>>>        address in the link-layer header will be an unicast
>> address.  It
>>>>        is up to to the system architecture as when to
>> transmit a IPv6
>>>>        multicast message as an link-layer unicast message,
>> as long as
>>>>        there is no real impact to the multicast communication.
>>>> 
>>>> This sentence is pretty vague. Especially "no real
>> impact", not sure
>>>> what that means. And what do you mean by "multicast communication".
>>>> 
>>>> Also, the reason you may want the system architecture to transmit
>>>> unicast, is that it has a positive impact on the
>> communication, right?
>>>> If whether you use unicast or not has no impact, then this would be
>>>> pointless ;)
>>>> 
>>> 
>>> :) My point is that, if the usage of the semantic is used
>> in the right away,
>>> there should be any impact to the multicast communication.
>> If I'm hosting
>>> two IPv6 VLAN's on the same 802.11 link, if the AP ensures
>> the RA's are
>>> segregated and sent to the right groups, its to me no
>> impact to multicast
>>> communication.  But, I see your point, this needs to worded
>> correctly. I
>>> will fix this in -01 version, posted it a hour back.
>> 
>> Sorry I was a bit late. I think the draft is good. Just trying to be a
>> bit difficult here :) But I think it can be made clearer.
>> 
>> Stig
>> 
>> 
>> 
>>

Re: AW: I-D Action:draft-gundavelli-v6ops-l2-unic… Sri Gundavelli
AW: I-D Action:draft-gundavelli-v6ops-l2-unicast-… Olaf.Bonness
Re: AW: I-D Action:draft-gundavelli-v6ops-l2-unic… Sri Gundavelli