IETF Logo Mail Archive

Re: Consensus call on adopting <draft-krishnan-6man-rs-mark-08.txt>

Suresh Krishnan <suresh.krishnan@ericsson.com> Fri, 22 October 2010 15:06 UTC

Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7AD2D3A6817 for <ipv6@core3.amsl.com>; Fri, 22 Oct 2010 08:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.529
X-Spam-Level:
X-Spam-Status: No, score=-103.529 tagged_above=-999 required=5 tests=[AWL=1.070, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zU2kjYy5bANW for <ipv6@core3.amsl.com>; Fri, 22 Oct 2010 08:06:23 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 071B63A67D9 for <ipv6@ietf.org>; Fri, 22 Oct 2010 08:06:22 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id o9MF7uCq010142 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 22 Oct 2010 10:08:00 -0500
Received: from [142.133.10.113] (147.117.20.213) by eusaamw0707.eamcs.ericsson.se (147.117.20.92) with Microsoft SMTP Server id 8.2.234.1; Fri, 22 Oct 2010 11:07:55 -0400
Message-ID: <4CC1A846.4030605@ericsson.com>
Date: Fri, 22 Oct 2010 11:05:42 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Philip Homburg <pch-6man@u-1.phicoh.com>
Subject: Re: Consensus call on adopting <draft-krishnan-6man-rs-mark-08.txt>
References: <3F7E0126-76FB-43BA-B25F-1EE226FA73AA@gmail.com> <79ECC38B-B7AD-47B1-B6A4-E0B4F75B91F1@gmail.com> <m21v7icp8p.wl%randy@psg.com> <m1P9IGH-0001fnC@stereo.hq.phicoh.net> <4CC19ACF.5070706@ericsson.com> <m1P9IZF-0001gMC@stereo.hq.phicoh.net> <4CC1A3A5.9040209@ericsson.com> <m1P9J7Y-0001VwC@stereo.hq.phicoh.net>
In-Reply-To: <m1P9J7Y-0001VwC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: IPv6 WG Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 15:06:24 -0000

Hi Philip,

On 10-10-22 11:01 AM, Philip Homburg wrote:
> In your letter dated Fri, 22 Oct 2010 10:45:57 -0400 you wrote:
>>> But now I'm a bit confused. Given that the AN now has to ability to originat
>> e
>>> RS messages, why is it forwarding the end-device' RS at all? Is that only to
>>> support SEND?
>> Exactly. The ability to send host-initiated RSs through is mainly for 
>> supporting SEND pass through, as this capability was deemed very 
>> important by the WG.
> 
> Then I guess the obvious next question is how this interacts with SEND if
> the original 3 RS messages are lost. 

The AN-initiated RSs in this case will not be SEND protected RSs (since 
we do not have the host's private key), but the edge router is still 
free to send SEND protected RAs back to the host in response to this RS. 
Then the host and the edge router can use SEND for protecting any 
further ND messages.

Thanks
Suresh

v2.23.0 | Report a Bug | By Email