RE: [16NG] ipv6 over ipv6cs document approval

"Premec, Domagoj" <domagoj.premec@siemens.com> Fri, 23 November 2007 15:16 UTC

Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvaGR-0004uV-Js; Fri, 23 Nov 2007 10:16:19 -0500
Received: from 16ng by megatron.ietf.org with local (Exim 4.43) id 1IvaGQ-0004uO-Bk for 16ng-confirm+ok@megatron.ietf.org; Fri, 23 Nov 2007 10:16:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IvaGQ-0004uG-2G for 16ng@ietf.org; Fri, 23 Nov 2007 10:16:18 -0500
Received: from mxs2.siemens.at ([194.138.12.133]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IvaGM-0003Gv-DE for 16ng@ietf.org; Fri, 23 Nov 2007 10:16:18 -0500
Received: from vies1kbx.sie.siemens.at ([158.226.129.82]) by mxs2.siemens.at with ESMTP id lANFGFG0029817; Fri, 23 Nov 2007 16:16:15 +0100
Received: from nets138a.ww300.siemens.net ([158.226.129.98]) by vies1kbx.sie.siemens.at (8.12.11.20060308/8.12.1) with ESMTP id lANFGCKt026162; Fri, 23 Nov 2007 16:16:12 +0100
Received: from zagh223a.ww300.siemens.net ([141.29.124.9]) by nets138a.ww300.siemens.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 23 Nov 2007 16:16:12 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [16NG] ipv6 over ipv6cs document approval
Date: Fri, 23 Nov 2007 16:16:09 +0100
Message-ID: <3C31CDD06342EA4A8137716247B1CD6802FBCEEE@zagh223a.ww300.siemens.net>
In-Reply-To: <d47344770711230408i206b0204u3ae3e73363940b0b@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [16NG] ipv6 over ipv6cs document approval
Thread-Index: Acgtya4RTfKU8bn/R1u3/q5tcPlW6AAGSDTQ
References: <d47344770711220101y3597825fnaeb77e155ce12a06@mail.gmail.com><C36BC142.4C82B%basavaraj.patil@nsn.com><d47344770711230155k2676cc6bsa07f7e7bb2159918@mail.gmail.com><4746AECE.4080402@piuha.net> <d47344770711230408i206b0204u3ae3e73363940b0b@mail.gmail.com>
From: "Premec, Domagoj" <domagoj.premec@siemens.com>
To: "Junghoon Jee" <junghoon.jee@gmail.com>
X-OriginalArrivalTime: 23 Nov 2007 15:16:12.0155 (UTC) FILETIME=[C84FACB0:01C82DE3]
X-purgate: clean
X-purgate: This mail is considered clean
X-purgate-type: clean
X-purgate-Ad: Checked for Spam by eleven - eXpurgate www.eXpurgate.net
X-purgate-ID: 149917::071123161615-6AF4BBB0-4FE9A286/0-0/0-15
X-purgate-size: 1160/999999
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

Hi Junghoon,

> To maintain the IP reachability through neighbor
> discovery packets, yes, I need to send them.

Host probes neighbor for reachability only when it has packets to send. 

> However, those packets can wake up idle/sleep SS.

Host in the idle mode will not have any packets for sending and thus will not initiate NUD.

domagoj


________________________________

	From: Junghoon Jee [mailto:junghoon.jee@gmail.com] 
	Sent: 23. studeni 2007 13:09
	To: Jari Arkko
	Cc: 16ng@ietf.org
	Subject: Re: [16NG] ipv6 over ipv6cs document approval
	
	
	To maintain the IP reachability through neighbor discovery packets, yes, I need to send them.
	However, those packets can wake up idle/sleep SS.
	What can we recommend in this situation?
	 
	Junghoon
	
	 
	2007/11/23, Jari Arkko <jari.arkko@piuha.net>et>: 


		>
		> >Because of the PtP link type there is no question about an MS being
		> transitioned out of Idle mode because of ND. 
		>
		> So, we should not send neighbor discovery packets in case of the IPv6CS?
		
		No, you send them when you need to.
		
		Jari
		
		




_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng