RE: speaking of ND Proxy and NBMA etc.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: speaking of ND Proxy and NBMA etc.
- To: "Hemant Singh (shemant)" <shemant at cisco.com>, Pekka Savola <pekkas at netcore.fi>
- Subject: RE: speaking of ND Proxy and NBMA etc.
- From: "Laganier, Julien" <julienl at qualcomm.com>
- Date: Wed, 18 Nov 2009 09:55:56 -0800
- Accept-language: en-US
- Acceptlanguage: en-US
- Cc: "draft-ietf-csi-proxy-send at tools.ietf.org" <draft-ietf-csi-proxy-send at tools.ietf.org>, "csi-chairs at tools.ietf.org" <csi-chairs at tools.ietf.org>, "ipv6 at ietf.org" <ipv6 at ietf.org>
- Delivered-to: ipv6 at core3.amsl.com
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl at qualcomm.com; q=dns/txt; s=qcdkim; t=1258566963; x=1290102963; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version:x-ironport-av; z=From:=20"Laganier,=20Julien"=20<julienl at qualcomm.com> |To:=20"Hemant=20Singh=20(shemant)"=20<shemant at cisco.com> ,=0D=0A=20=20=20=20=20=20=20=20Pekka=20Savola=0D=0A=09<pe kkas at netcore.fi>|CC:=20"ipv6 at ietf.org"=20<ipv6 at ietf.org>, =0D=0A=20=20=20=20=20=20=20=20"draft-ietf-csi-proxy-send@ tools.ietf.org"=0D=0A=09<draft-ietf-csi-proxy-send at tools. ietf.org>,=0D=0A=20=20=20=20=20=20=20=20"csi-chairs at tools .ietf.org"=0D=0A=09<csi-chairs at tools.ietf.org>|Date:=20We d,=2018=20Nov=202009=2009:55:56=20-0800|Subject:=20RE:=20 speaking=20of=20ND=20Proxy=20and=20NBMA=20etc. |Thread-Topic:=20speaking=20of=20ND=20Proxy=20and=20NBMA =20etc.|Thread-Index:=20AcpjZIjQaA5t5jzSSHCuO3L0JeeG6AAGd 0NAAR4LckAAIEp3UAAAFChA|Message-ID:=20<BF345F63074F8040B5 8C00A186FCA57F1C65FB25D4 at NALASEXMB04.na.qualcomm.com> |References:=20<AF742F21C1FCEE4DAB7F4842ABDC511C1C2ECA at XM B-RCD-114.cisco.com><alpine.LRH.2.00.0911120848570.26415@ netcore.fi>=0D=0A=20<AF742F21C1FCEE4DAB7F4842ABDC511C1C33 67 at XMB-RCD-114.cisco.com>=0D=0A=20<BF345F63074F8040B58C00 A186FCA57F1C65FB258B at NALASEXMB04.na.qualcomm.com>=0D=0A =20<AF742F21C1FCEE4DAB7F4842ABDC511C2EEA88 at XMB-RCD-114.ci sco.com>|In-Reply-To:=20<AF742F21C1FCEE4DAB7F4842ABDC511C 2EEA88 at XMB-RCD-114.cisco.com>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5806"=3B=20a=3D"27898143"; bh=KahI8seoYn+Uiul4nsrcJyczgGwUSi3Mqz1tcazj5MM=; b=G1psCtPyw3ul6LLsXtGnsscIFyRrhRiBSrXjgEL7r16OVd9KIlPB8fl1 T+BTijzOJOG4nxJbk4AupnDSgDvvc0wjW81FYBvUlyPw0v2lO9f3XHl4M jSq5FHZcADFGwugJ15GApVPllsIXH/n6FRUH5ipv99oNF24mql2EgFSAp 8=;
- In-reply-to: <AF742F21C1FCEE4DAB7F4842ABDC511C2EEA88 at XMB-RCD-114.cisco.com>
- List-archive: <http://www.ietf.org/mail-archive/web/ipv6>
- List-help: <mailto:ipv6-request@ietf.org?subject=help>
- List-id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
- List-post: <mailto:ipv6@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
- References: <AF742F21C1FCEE4DAB7F4842ABDC511C1C2ECA at XMB-RCD-114.cisco.com><alpine.LRH.2.00.0911120848570.26415 at netcore.fi> <AF742F21C1FCEE4DAB7F4842ABDC511C1C3367 at XMB-RCD-114.cisco.com> <BF345F63074F8040B58C00A186FCA57F1C65FB258B at NALASEXMB04.na.qualcomm.com> <AF742F21C1FCEE4DAB7F4842ABDC511C2EEA88 at XMB-RCD-114.cisco.com>
- Thread-index: AcpjZIjQaA5t5jzSSHCuO3L0JeeG6AAGd0NAAR4LckAAIEp3UAAAFChA
- Thread-topic: speaking of ND Proxy and NBMA etc.
Hemant,
Right - I understand that some deployments do not require SEND security.
As a side note, draft-ietf-csi-proxy-send-01 has just entered WGLC in the CSI WG, reviews by interested parties would be appreciated!
Thank you.
--julien
> -----Original Message-----
> From: Hemant Singh (shemant) [mailto:shemant at cisco.com]
> Sent: Wednesday, November 18, 2009 9:53 AM
> To: Laganier, Julien; Pekka Savola
> Cc: ipv6 at ietf.org; draft-ietf-csi-proxy-send at tools.ietf.org; csi-
> chairs at tools.ietf.org
> Subject: RE: speaking of ND Proxy and NBMA etc.
>
> Julien,
>
> Thanks - we will update our draft to change the info that now the CSI
> group is working on SEND extensions for ND Proxy and it's Work in
> Progress. However, one original intent of our draft is still valid
> that
> some deployments want to use ND Proxy but will not use SEND.
>
> Hemant
>
> -----Original Message-----
> From: Laganier, Julien [mailto:julienl at qualcomm.com]
> Sent: Tuesday, November 17, 2009 9:31 PM
> To: Hemant Singh (shemant); Pekka Savola
> Cc: ipv6 at ietf.org; draft-ietf-csi-proxy-send at tools.ietf.org;
> csi-chairs at tools.ietf.org
> Subject: RE: speaking of ND Proxy and NBMA etc.
>
> Hemant,
>
> The CSI WG has been chartered in 2008 to develop an ND proxy support
> for
> SEND and has a corresponding work item:
>
> <http://tools.ietf.org/html/draft-ietf-csi-proxy-send-01>
>
> --julien
>
> > -----Original Message-----
> > From: ipv6-bounces at ietf.org [mailto:ipv6-bounces at ietf.org] On Behalf
> Of
> > Hemant Singh (shemant)
> > Sent: Thursday, November 12, 2009 2:13 AM
> > To: Pekka Savola
> > Cc: ipv6 at ietf.org
> > Subject: RE: speaking of ND Proxy and NBMA etc.
> >
> > Yes. Cable access concentrators (also called a CMTS (Cable Modem
> > Termination System)) for ipv4 support an ARP Proxy. So it was
> natural
> > when the CMTS moved to also supporting IPv6, having the CMTS support
> ND
> > Proxy was a natural transition. Two different CMTS vendors (one is
> > Cisco) support ND Proxy as of 2007. Cable deployment is a NBMA
> network
> > where client behind our cable modem cannot communicate directly to
> each
> > other. So the CMTS ND Proxy catches DAD duplicates and sends an NA
> and
> > the CMTS also responds to address resolution NS's with an NA. That
> is
> > the extent of the ND Proxy on cable access concentrators. Cable data
> > standards in Docsis 3.0 have also recommended ND Proxy. Note also
> that
> > 6lowpan has also recommended ND Proxy in their draft -
> > http://www.ietf.org/id/draft-ietf-6lowpan-nd-07.txt. The v6ops IPv6
> CE
> > Home Router has recommended ND Proxy for the router. A v6ops
> document
> > cannot reference an Experimental RFC - this was the first motive
> behind
> > moving the ND Proxy RFC to be a Standards Track document.
> >
> > I personally think RFC 4389 is well shaken out for a doc - as we say
> in
> > our new short note, the only reason they didn't make the ND Proxy doc
> a
> > Standards Track doc because ND Proxy did not support SEND extensions.
> > The SEND extensions was work TBD with another IETF WG but that group
> is,
> > I think, 4 years and counting for not taking this work. But there
> are
> > networks that need ND Proxy without use of SEND.
> >
> > Hemant
> >
> > -----Original Message-----
> > From: Pekka Savola [mailto:pekkas at netcore.fi]
> > Sent: Thursday, November 12, 2009 3:51 PM
> > To: Hemant Singh (shemant)
> > Cc: ipv6 at ietf.org
> > Subject: Re: speaking of ND Proxy and NBMA etc.
> >
> > On Wed, 11 Nov 2009, Hemant Singh (shemant) wrote:
> > > http://www.ietf.org/id/draft-wbeebee-6man-nd-proxy-std-00.txt
> >
> > Do we already have implementations? What are the implementation
> > experiences? Were all the features of the spec useful, or should
> > something be changed (added, removed, clarified)?
> >
> > This is not procedurally required for PS, but if there are a lot of
> > implementations already, this would be a strong argument for going to
> > PS.
> >
> > --
> > Pekka Savola "You each name yourselves king, yet the
> > Netcore Oy kingdom bleeds."
> > Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6 at ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.