From ipv6-bounces@ietf.org  Thu Jan  1 18:58:06 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E89D93A67FD;
	Thu,  1 Jan 2009 18:58:05 -0800 (PST)
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 1FF6C3A67FD
	for <ipv6@core3.amsl.com>; Thu,  1 Jan 2009 18:58:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.547
X-Spam-Level: 
X-Spam-Status: No, score=-5.547 tagged_above=-999 required=5 tests=[AWL=1.051, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 NI2JAeeiVe1c for <ipv6@core3.amsl.com>;
	Thu,  1 Jan 2009 18:58:02 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 6F65D3A67B0
	for <ipv6@ietf.org>; Thu,  1 Jan 2009 18:58:02 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,316,1228089600"; d="scan'208,217";a="32492456"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 02 Jan 2009 02:57:50 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n022vneG020530; 
	Thu, 1 Jan 2009 21:57:49 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n022vnmK001487;
	Fri, 2 Jan 2009 02:57:49 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Jan 2009 21:57:49 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: DAD failure for global IPv6 addresses?
Date: Thu, 1 Jan 2009 21:57:49 -0500
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0632C022@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <808F2ECE7425024994976AC3D44BDCF4C8B8C4@vaebe108.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: DAD failure for global IPv6 addresses?
Thread-Index: Aclrsk2d15kwmQ7MSISbw/7KOnD4QwAzfM2Q
References: <808F2ECE7425024994976AC3D44BDCF4C8B8C4@vaebe108.NOE.Nokia.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: <Peter.Hunt@nokia.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 02 Jan 2009 02:57:49.0835 (UTC)
	FILETIME=[E5C89DB0:01C96C85]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4714; t=1230865069;
	x=1231729069; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.
	com>
	|Subject:=20RE=3A=20DAD=20failure=20for=20global=20IPv6=20a
	ddresses? |Sender:=20
	|To:=20<Peter.Hunt@nokia.com>,=20<ipv6@ietf.org>;
	bh=uBxSiuv6dzIn8Ln0HrbSN7v5msmaq+2uL1jHiDZhcio=;
	b=cmE1hWlr80Y7hX94lBA+F54GlQZ8Hf2j77S/jzPzxTEhsUftST4BQHfBZr
	vkFVCEZxd/BIHuiXIHePxVqz2xRm3VR16NI/z+agXOdGMDiFsHeq3BgwjKIQ
	bEd/ZFcpKG;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0842477491=="
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0842477491==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C96C85.E58691E6"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C96C85.E58691E6
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Sorry, your email sounds a little confusing to me.  Specifically, are
you talking about a network interface on a router where the interface
fails DAD during acquiring a global IPv6 address?  Or are you talking
about a node (potentially a host) in an IPv6 routed network where a
network interface on the node failed DAD for a global IPv6 address?
Also, I take it when you say "DAD failed", you mean the sending
interface of the DAD has received an NA signaling a duplicate for the
global address?
=20
If a duplicate for a global address is found in the network, then the
network interface that send the DAD should not use the global IPv6
address to source any packets that need a global address for source.
See text like the following snipped from section 5.4 of RFC 4861
=20
[The procedure for detecting duplicate addresses uses Neighbor
  Solicitation and Advertisement messages as described below.  If a
  duplicate address is discovered during the procedure, the address
  cannot be assigned to the interface. ]
=20
Nowhere does the text above differentiate between a link-local or a
global address, so the rule applies to a global address a well.
=20
Happy New Year to everyone on this mailer.
=20
Hemant



------_=_NextPart_001_01C96C85.E58691E6
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=3Dltr><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3492" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D755251702-02012009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sorry, your email sounds a little confusing to =
me.&nbsp;=20
Specifically, are you talking about a network interface on a router =
where the=20
interface fails DAD during acquiring a global IPv6 address?&nbsp; Or are =
you=20
talking about a node (potentially a host) in an IPv6 routed network =
where a=20
network interface on the node failed DAD for a global IPv6 =
address?&nbsp; Also,=20
I take it when you say "DAD failed", you mean the sending interface of =
the DAD=20
has received an NA signaling a duplicate for the global=20
address?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009>If a duplicate for a global address is found =
in the=20
network, then the network interface that send the DAD should not use the =
global=20
IPv6 address to source any packets that need a global address for =
source.&nbsp;=20
See text like the following snipped from section 5.4 of RFC=20
4861</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D755251702-02012009><FONT=20
size=3D3><FONT size=3D2>[</FONT>The procedure for detecting duplicate =
addresses uses=20
Neighbor<BR>&nbsp;&nbsp;Solicitation and Advertisement messages as =
described=20
below.&nbsp; If a<BR>&nbsp;&nbsp;duplicate address is discovered during =
the=20
procedure, the address<BR>&nbsp;&nbsp;cannot be assigned to the =
interface.=20
]</FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009>Nowhere does the text above differentiate =
between a=20
link-local or a global address, so the rule applies to a global address =
a=20
well.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009>Happy New Year to everyone on this=20
mailer.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009>Hemant</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT><BR></DIV></BODY></HTML>

------_=_NextPart_001_01C96C85.E58691E6--

--===============0842477491==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0842477491==--


From ipv6-bounces@ietf.org  Thu Jan  1 19:02:36 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 923673A69FF;
	Thu,  1 Jan 2009 19:02:36 -0800 (PST)
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 59B593A69FF
	for <ipv6@core3.amsl.com>; Thu,  1 Jan 2009 19:02:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.757
X-Spam-Level: 
X-Spam-Status: No, score=-5.757 tagged_above=-999 required=5 tests=[AWL=0.841, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 OUliQl-jtFOZ for <ipv6@core3.amsl.com>;
	Thu,  1 Jan 2009 19:02:34 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 42FA73A6999
	for <ipv6@ietf.org>; Thu,  1 Jan 2009 19:02:34 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.36,316,1228089600"; d="scan'208,217";a="32492708"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 02 Jan 2009 03:02:22 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n0232MWL021855; 
	Thu, 1 Jan 2009 22:02:22 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n0232Mj5023574;
	Fri, 2 Jan 2009 03:02:22 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 1 Jan 2009 22:02:21 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: DAD failure for global IPv6 addresses?
Date: Thu, 1 Jan 2009 22:02:21 -0500
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0632C023@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0632C022@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: DAD failure for global IPv6 addresses?
Thread-Index: Aclrsk2d15kwmQ7MSISbw/7KOnD4QwAzfM2QAAGL1EA=
References: <808F2ECE7425024994976AC3D44BDCF4C8B8C4@vaebe108.NOE.Nokia.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0632C022@xmb-rtp-20e.amer.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, <Peter.Hunt@nokia.com>,
	<ipv6@ietf.org>
X-OriginalArrivalTime: 02 Jan 2009 03:02:21.0765 (UTC)
	FILETIME=[87DDD750:01C96C86]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5987; t=1230865342;
	x=1231729342; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.
	com>
	|Subject:=20RE=3A=20DAD=20failure=20for=20global=20IPv6=20a
	ddresses? |Sender:=20
	|To:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.co
	m>,=20<Peter.Hunt@nokia.com>,=0A=20=20=20=20=20=20=20=20<ipv
	6@ietf.org>; bh=9kBqu1qwC/1Gb3VD0BTuYaRqEZYGSqCiVsURyDVQp9s=;
	b=G0K7Ji3CVqKQlsJllsAzWlrIvt+BUuV9zaQm3VbsecVwjEne8ffj+KbrMM
	M/BhLzVmWW8p1+EW/AHUZ4V9x1Anteb+AoK+1SXjEdLSPbQccdc+7vcfExqj
	P1xpWljUiV;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0952817590=="
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0952817590==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C96C86.87AB0FC2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C96C86.87AB0FC2
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Sorry, I meant, section 5.4 of RFC 4862, not RFC 4861.
=20
Hemant

________________________________

From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
Hemant Singh (shemant)
Sent: Thursday, January 01, 2009 9:58 PM
To: Peter.Hunt@nokia.com; ipv6@ietf.org
Subject: RE: DAD failure for global IPv6 addresses?


Sorry, your email sounds a little confusing to me.  Specifically, are
you talking about a network interface on a router where the interface
fails DAD during acquiring a global IPv6 address?  Or are you talking
about a node (potentially a host) in an IPv6 routed network where a
network interface on the node failed DAD for a global IPv6 address?
Also, I take it when you say "DAD failed", you mean the sending
interface of the DAD has received an NA signaling a duplicate for the
global address?
=20
If a duplicate for a global address is found in the network, then the
network interface that send the DAD should not use the global IPv6
address to source any packets that need a global address for source.
See text like the following snipped from section 5.4 of RFC 4861
=20
[The procedure for detecting duplicate addresses uses Neighbor
  Solicitation and Advertisement messages as described below.  If a
  duplicate address is discovered during the procedure, the address
  cannot be assigned to the interface. ]
=20
Nowhere does the text above differentiate between a link-local or a
global address, so the rule applies to a global address a well.
=20
Happy New Year to everyone on this mailer.
=20
Hemant



------_=_NextPart_001_01C96C86.87AB0FC2
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=3Dltr><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3492" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D066420103-02012009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sorry, I meant, section 5.4 of RFC 4862, not =
RFC=20
4861.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D066420103-02012009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D066420103-02012009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hemant</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> ipv6-bounces@ietf.org=20
[mailto:ipv6-bounces@ietf.org] <B>On Behalf Of </B>Hemant Singh=20
(shemant)<BR><B>Sent:</B> Thursday, January 01, 2009 9:58 =
PM<BR><B>To:</B>=20
Peter.Hunt@nokia.com; ipv6@ietf.org<BR><B>Subject:</B> RE: DAD failure =
for=20
global IPv6 addresses?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D755251702-02012009><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Sorry, your email sounds a little confusing to =
me.&nbsp;=20
Specifically, are you talking about a network interface on a router =
where the=20
interface fails DAD during acquiring a global IPv6 address?&nbsp; Or are =
you=20
talking about a node (potentially a host) in an IPv6 routed network =
where a=20
network interface on the node failed DAD for a global IPv6 =
address?&nbsp; Also,=20
I take it when you say "DAD failed", you mean the sending interface of =
the DAD=20
has received an NA signaling a duplicate for the global=20
address?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009>If a duplicate for a global address is found =
in the=20
network, then the network interface that send the DAD should not use the =
global=20
IPv6 address to source any packets that need a global address for =
source.&nbsp;=20
See text like the following snipped from section 5.4 of RFC=20
4861</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D755251702-02012009><FONT=20
size=3D3><FONT size=3D2>[</FONT>The procedure for detecting duplicate =
addresses uses=20
Neighbor<BR>&nbsp;&nbsp;Solicitation and Advertisement messages as =
described=20
below.&nbsp; If a<BR>&nbsp;&nbsp;duplicate address is discovered during =
the=20
procedure, the address<BR>&nbsp;&nbsp;cannot be assigned to the =
interface.=20
]</FONT></SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009>Nowhere does the text above differentiate =
between a=20
link-local or a global address, so the rule applies to a global address =
a=20
well.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009>Happy New Year to everyone on this=20
mailer.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D755251702-02012009>Hemant</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT><BR></DIV></BODY></HTML>

------_=_NextPart_001_01C96C86.87AB0FC2--

--===============0952817590==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0952817590==--


From ipv6-bounces@ietf.org  Fri Jan  2 10:20:58 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 857DB3A681D;
	Fri,  2 Jan 2009 10:20:58 -0800 (PST)
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 CFFDE3A681D
	for <ipv6@core3.amsl.com>; Fri,  2 Jan 2009 10:20:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.202
X-Spam-Level: 
X-Spam-Status: No, score=-5.202 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396,
	RCVD_IN_DNSWL_MED=-4]
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 8MWR8BwT2YiM for <ipv6@core3.amsl.com>;
	Fri,  2 Jan 2009 10:20:56 -0800 (PST)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 382323A66B4
	for <ipv6@ietf.org>; Fri,  2 Jan 2009 10:20:55 -0800 (PST)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	n02IKIU0007966; Fri, 2 Jan 2009 20:20:19 +0200
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 2 Jan 2009 20:20:17 +0200
Received: from vaebe108.NOE.Nokia.com ([10.160.244.69]) by
	vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 2 Jan 2009 20:20:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: DAD failure for global IPv6 addresses?
Date: Fri, 2 Jan 2009 20:20:17 +0200
Message-ID: <808F2ECE7425024994976AC3D44BDCF4C8B8C5@vaebe108.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: DAD failure for global IPv6 addresses?
thread-index: Aclrsk2d15kwmQ7MSISbw/7KOnD4QwAzfM2QACDUEvk=
References: <808F2ECE7425024994976AC3D44BDCF4C8B8C4@vaebe108.NOE.Nokia.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0632C022@xmb-rtp-20e.amer.cisco.com>
From: <Peter.Hunt@nokia.com>
To: <shemant@cisco.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 02 Jan 2009 18:20:17.0842 (UTC)
	FILETIME=[C3C44120:01C96D06]
X-Nokia-AV: Clean
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1274023021=="
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1274023021==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C96D06.C3BCC6C5"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C96D06.C3BCC6C5
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hermant,
=20
thanks very much for your reply.
=20
To answer your questions, I am talking about a network interface on a =
router where the interface fails DAD for a global IPv6 address. "DAD =
failure" means that the interface received an NA or a DAD NS for the =
tentative global address, signalling a duplicate on another system on =
that link.
=20
I understand that the global address is not assigned to the interface, =
but I'm really asking about the implications of that on the behaviour of =
the router.
=20
The RFC states that the failure of a link-local address causes all IPv6 =
traffic to/from that interface to be dropped, and this led me to wonder =
about the effect of a global address DAD failure on traffic.
=20
>From the RFC excerpt you gave, I would infer that on DAD failure of a =
global address, the router doesn't install the address, and forwards all =
traffic to/from that network based on the contents of its forwarding =
table. It does no special filtering of packets that are sourced from or =
destined to that network.
=20
Do you agree?
=20
Thanks,
Peter

________________________________

From: ext Hemant Singh (shemant) [mailto:shemant@cisco.com]
Sent: Thu 1/1/2009 6:57 PM
To: Hunt Peter (Nokia-S&S/MtView); ipv6@ietf.org
Subject: RE: DAD failure for global IPv6 addresses?


Sorry, your email sounds a little confusing to me.  Specifically, are =
you talking about a network interface on a router where the interface =
fails DAD during acquiring a global IPv6 address?  Or are you talking =
about a node (potentially a host) in an IPv6 routed network where a =
network interface on the node failed DAD for a global IPv6 address?  =
Also, I take it when you say "DAD failed", you mean the sending =
interface of the DAD has received an NA signaling a duplicate for the =
global address?
=20
If a duplicate for a global address is found in the network, then the =
network interface that send the DAD should not use the global IPv6 =
address to source any packets that need a global address for source.  =
See text like the following snipped from section 5.4 of RFC 4861
=20
[The procedure for detecting duplicate addresses uses Neighbor
  Solicitation and Advertisement messages as described below.  If a
  duplicate address is discovered during the procedure, the address
  cannot be assigned to the interface. ]
=20
Nowhere does the text above differentiate between a link-local or a =
global address, so the rule applies to a global address a well.
=20
Happy New Year to everyone on this mailer.
=20
Hemant



------_=_NextPart_001_01C96D06.C3BCC6C5
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.6001.18183" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText88240 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" color=3D#000000 =
size=3D2>Hermant,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>thanks very much for =
your reply.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>To answer your =
questions, I am talking about a network interface on a router where the =
interface fails DAD for a global IPv6 address. "DAD failure" means that =
the interface received an NA or a DAD NS for the tentative global =
address, signalling a duplicate on another system on that =
link.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>I understand that the =
global address is not assigned to the interface, but I'm really asking =
about the implications of that on the behaviour of the =
router.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>The RFC states that =
the failure of a link-local address causes all IPv6 traffic to/from that =
interface to be dropped, and this led me to wonder about the effect of a =
global address DAD failure on traffic.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>From the RFC excerpt =
you gave, I would infer that on DAD failure of a global address, the =
router doesn't install the address, and forwards all traffic to/from =
that network based on the contents of its forwarding table. It does no =
special filtering of packets that are sourced from or destined to that =
network.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>Do you =
agree?</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>Thanks,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" =
size=3D2>Peter</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> ext Hemant Singh (shemant) =
[mailto:shemant@cisco.com]<BR><B>Sent:</B> Thu 1/1/2009 6:57 =
PM<BR><B>To:</B> Hunt Peter (Nokia-S&amp;S/MtView); =
ipv6@ietf.org<BR><B>Subject:</B> RE: DAD failure for global IPv6 =
addresses?<BR></FONT><BR></DIV>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr align=3Dleft><SPAN class=3D755251702-02012009><FONT =
face=3DArial color=3D#0000ff size=3D2>Sorry, your email sounds a little =
confusing to me.&nbsp; Specifically, are you talking about a network =
interface on a router where the interface fails DAD during acquiring a =
global IPv6 address?&nbsp; Or are you talking about a node (potentially =
a host) in an IPv6 routed network where a network interface on the node =
failed DAD for a global IPv6 address?&nbsp; Also, I take it when you say =
"DAD failed", you mean the sending interface of the DAD has received an =
NA signaling a duplicate for the global address?</FONT></SPAN></DIV>=0A=
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN =
class=3D755251702-02012009>If a duplicate for a global address is found =
in the network, then the network interface that send the DAD should not =
use the global IPv6 address to source any packets that need a global =
address for source.&nbsp; See text like the following snipped from =
section 5.4 of RFC 4861</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN =
class=3D755251702-02012009></SPAN></FONT></FONT></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D755251702-02012009><FONT size=3D3><FONT size=3D2>[</FONT>The =
procedure for detecting duplicate addresses uses =
Neighbor<BR>&nbsp;&nbsp;Solicitation and Advertisement messages as =
described below.&nbsp; If a<BR>&nbsp;&nbsp;duplicate address is =
discovered during the procedure, the address<BR>&nbsp;&nbsp;cannot be =
assigned to the interface. ]</FONT></SPAN></FONT></FONT></DIV>=0A=
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN =
class=3D755251702-02012009></SPAN></FONT></FONT></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN =
class=3D755251702-02012009>Nowhere does the text above differentiate =
between a link-local or a global address, so the rule applies to a =
global address a well.</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN =
class=3D755251702-02012009></SPAN></FONT></FONT></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN =
class=3D755251702-02012009>Happy New Year to everyone on this =
mailer.</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN =
class=3D755251702-02012009></SPAN></FONT></FONT></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN =
class=3D755251702-02012009>Hemant</SPAN></FONT></FONT></FONT></DIV>=0A=
<DIV><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT><BR></DIV></DIV></BODY></HTML>
------_=_NextPart_001_01C96D06.C3BCC6C5--

--===============1274023021==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1274023021==--


From ipv6-bounces@ietf.org  Fri Jan  2 12:06:59 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0C3F83A6979;
	Fri,  2 Jan 2009 12:06:59 -0800 (PST)
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 DE6513A6979
	for <ipv6@core3.amsl.com>; Fri,  2 Jan 2009 12:06:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 Qt0ZhbQvnY8X for <ipv6@core3.amsl.com>;
	Fri,  2 Jan 2009 12:06:56 -0800 (PST)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31])
	by core3.amsl.com (Postfix) with ESMTP id 1BEEA3A6879
	for <ipv6@ietf.org>; Fri,  2 Jan 2009 12:06:55 -0800 (PST)
Received: by yw-out-2324.google.com with SMTP id 3so2858672ywj.49
	for <ipv6@ietf.org>; Fri, 02 Jan 2009 12:06:43 -0800 (PST)
Received: by 10.151.42.6 with SMTP id u6mr32640467ybj.22.1230926803615;
	Fri, 02 Jan 2009 12:06:43 -0800 (PST)
Received: by 10.150.177.7 with HTTP; Fri, 2 Jan 2009 12:06:43 -0800 (PST)
Message-ID: <67099930901021206h3caea085j2e26a25a4a25d083@mail.gmail.com>
Date: Fri, 2 Jan 2009 12:06:43 -0800
From: "Erik Kline" <ekline@ekline.com>
To: Peter.Hunt@nokia.com
Subject: Re: DAD failure for global IPv6 addresses?
In-Reply-To: <808F2ECE7425024994976AC3D44BDCF4C8B8C5@vaebe108.NOE.Nokia.com>
MIME-Version: 1.0
Content-Disposition: inline
References: <808F2ECE7425024994976AC3D44BDCF4C8B8C4@vaebe108.NOE.Nokia.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0632C022@xmb-rtp-20e.amer.cisco.com>
	<808F2ECE7425024994976AC3D44BDCF4C8B8C5@vaebe108.NOE.Nokia.com>
Cc: 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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

> From the RFC excerpt you gave, I would infer that on DAD failure of a global
> address, the router doesn't install the address, and forwards all traffic
> to/from that network based on the contents of its forwarding table. It does
> no special filtering of packets that are sourced from or destined to that
> network.
>
> Do you agree?
>
> Thanks,
> Peter

This sounds to me like a recipe for a hard-to-debug problem.

I assume that when this DAD failure happens you'd have to stop sending
RAs and responding to RSs (or ...?).  So the only way the router
should be seeing packets destined to this interface would be either
some misconfiguration OR a cached RA/RS response where the max/valid
lifetimes had not yet expired AND a neighbor re-discovery had not yet
been performed.

I haven't computed how long this could in theory persist.  But again,
regardless of any technical correctness, it sounds like the making of
a weird debugging problem.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


From ipv6-bounces@ietf.org  Sat Jan  3 12:52:43 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A3D593A688E;
	Sat,  3 Jan 2009 12:52:43 -0800 (PST)
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 0E6A93A68F2
	for <ipv6@core3.amsl.com>; Sat,  3 Jan 2009 04:29:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001,
	HTML_OBFUSCATE_05_10=0.001]
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 vx-gPAVOVv2K for <ipv6@core3.amsl.com>;
	Sat,  3 Jan 2009 04:29:24 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234])
	by core3.amsl.com (Postfix) with ESMTP id 20E063A686C
	for <ipv6@ietf.org>; Sat,  3 Jan 2009 04:29:23 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id b25so6042425rvf.49
	for <ipv6@ietf.org>; Sat, 03 Jan 2009 04:29:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to
	:subject:mime-version:content-type;
	bh=7ups9ELpxuwsKGGEVkPKJzc34o+LpOSsdfWDvPyIbwM=;
	b=ISBGSi1ibVQepahr0L3GB5P+5HJAPxw2jSv1ASIlZQSJ5fTcsSnOb4EhkQEKk1MXtf
	vJ4AXil2TerDpx5mJ2FbqKpWB1n7zeNNeeuMR80zK/ubzo5b4SQ5h1TKGhkL0ibFwigA
	MDLXp548NAnQrNOzN2eRr2/zMUBB+8bllkRVE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:mime-version:content-type;
	b=hFUMXrUidyXJqyKtcrTfgnP6TAADJk9hYJaIptV1++8miZo0W8dvaTiizODHU+xqRN
	66/PvxDQzi5yDnqzv8QHS9WAVnUzGgaJuBFzj09sdZgZyny83klnVsBgX3Dwhz65RlOK
	vMx9jZ4S6xeEoZ3ajxSDFCMNk4GQeV+wL849E=
Received: by 10.141.115.20 with SMTP id s20mr9313105rvm.255.1230985750470;
	Sat, 03 Jan 2009 04:29:10 -0800 (PST)
Received: by 10.141.194.9 with HTTP; Sat, 3 Jan 2009 04:29:10 -0800 (PST)
Message-ID: <7aea9ec0901030429h162f10c1k859f01584f2454b6@mail.gmail.com>
Date: Sat, 3 Jan 2009 17:59:10 +0530
From: "prejeeth kaladharan" <prejeeth@gmail.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: icmpv6 draft doubt
MIME-Version: 1.0
X-Mailman-Approved-At: Sat, 03 Jan 2009 12:52:42 -0800
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0973544040=="
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

--===============0973544040==
Content-Type: multipart/alternative; 
	boundary="----=_Part_179068_2242004.1230985750459"

------=_Part_179068_2242004.1230985750459
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi All,

With regard to RFC 4443 erratta,

*http://www.rfc-editor.org/errata_search.php?rfc=4443*

*o  Appendix A contains the change item:*
* - "Added specification that all ICMP error messages shall have
exactly**32 bits of type-specific data, so that receivers can reliably
find
** the embedded invoking packet even when they don't recognize the**ICMP
message Type**"*

* *Please let me know if anything additional needs to be taken care by
existing implementations to support the above said information, with regard
to RFC 4443 compliance, since **the previous ICMPv6 draft already had a 32
bit type specific information in its ICMPv6 message format.

With regards,

Prejeeth.K

------=_Part_179068_2242004.1230985750459
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi All,<br><br><font color=3D"black" size=3D"2" face=3D"Helv"><span style=
=3D"font-size: 10pt; font-family: Helv; color: black;" lang=3D"EN-US"></spa=
n></font><font color=3D"black" size=3D"2" face=3D"Helv"><span style=3D"font=
-size: 10pt; font-family: Helv; color: black;" lang=3D"EN-US">With regard t=
o RFC 4443 erratta,</span></font>

<p style=3D"margin-left: 0cm; line-height: 12pt;"><u><font color=3D"blue" s=
ize=3D"2" face=3D"Helv"><span style=3D"font-size: 10pt; font-family: Helv; =
color: blue;" lang=3D"EN-US"><a href=3D"http://www.rfc-editor.org/errata_se=
arch.php?rfc=3D4443" target=3D"_blank">http://www.rfc-editor.org/errata_sea=
rch.php?rfc=3D4443</a></span></font></u></p>




<p style=3D"margin-left: 0cm; line-height: 12pt;"><i><font color=3D"black" =
size=3D"3" face=3D"Courier"><span style=3D"font-size: 12pt; font-family: Co=
urier; color: black; font-style: italic;" lang=3D"EN-US">o&nbsp; Appendix A=
 contains the change
item:</span></font></i></p><i><font color=3D"black" size=3D"3" face=3D"Cour=
ier"><span style=3D"font-size: 12pt; font-family: Courier; color: black; fo=
nt-style: italic;" lang=3D"EN-US"> - &quot;Added specification that
all ICMP error messages shall have exactly</span></font></i><i><font color=
=3D"black" size=3D"3" face=3D"Courier"><span style=3D"font-size: 12pt; font=
-family: Courier; color: black; font-style: italic;" lang=3D"EN-US"> 32 bit=
s of
type-specific data, so that receivers can reliably find</span></font></i><i=
><font color=3D"black" size=3D"3" face=3D"Courier"><span style=3D"font-size=
: 12pt; font-family: Courier; color: black; font-style: italic;" lang=3D"EN=
-US"> the embedded
invoking packet even when they don&#39;t recognize the</span></font></i><i>=
<font color=3D"black" size=3D"3" face=3D"Courier"><span style=3D"font-size:=
 12pt; font-family: Courier; color: black; font-style: italic;" lang=3D"EN-=
US">ICMP message
Type</span></font></i><i><font color=3D"black" size=3D"3" face=3D"Courier">=
<span style=3D"font-size: 12pt; font-family: Courier; color: black; font-st=
yle: italic;" lang=3D"EN-US">&quot;</span></font></i><p style=3D"margin-lef=
t: 0cm; line-height: 12pt;">
<i><font color=3D"black" size=3D"3" face=3D"Courier"><span style=3D"font-si=
ze: 12pt; font-family: Courier; color: black; font-style: italic;" lang=3D"=
EN-US">&nbsp;</span></font></i><font color=3D"black" size=3D"3" face=3D"Cou=
rier"><span style=3D"font-size: 12pt; line-height: 150%; font-family: Couri=
er; color: black;" lang=3D"EN-US">Please let me know if anything additional
needs to be taken care by existing implementations to support the above sai=
d
information, with regard to RFC 4443 compliance, since </span></font><i><fo=
nt color=3D"black" size=3D"3" face=3D"Courier"><span style=3D"font-size: 12=
pt; font-family: Courier; color: black; font-style: italic;" lang=3D"EN-US"=
></span></font></i><font color=3D"black" size=3D"3" face=3D"Courier"><span =
style=3D"font-size: 12pt; line-height: 150%; font-family: Courier; color: b=
lack;" lang=3D"EN-US">t</span></font><font color=3D"black" size=3D"3" face=
=3D"Courier"><span style=3D"font-size: 12pt; line-height: 150%; font-family=
: Courier; color: black;" lang=3D"EN-US">he previous </span></font><font co=
lor=3D"black" size=3D"3" face=3D"Courier"><span style=3D"font-size: 12pt; l=
ine-height: 150%; font-family: Courier; color: black;" lang=3D"EN-US">ICMP<=
/span></font><font color=3D"black" size=3D"3" face=3D"Courier"><span style=
=3D"font-size: 12pt; line-height: 150%; font-family: Courier; color: black;=
" lang=3D"EN-US">v6 draf</span></font><font color=3D"black" size=3D"3" face=
=3D"Courier"><span style=3D"font-size: 12pt; line-height: 150%; font-family=
: Courier; color: black;" lang=3D"EN-US">t already had a 32 bi</span></font=
><font color=3D"black" size=3D"3" face=3D"Courier"><span style=3D"font-size=
: 12pt; line-height: 150%; font-family: Courier; color: black;" lang=3D"EN-=
US">t </span></font><font color=3D"black" size=3D"3" face=3D"Courier"><span=
 style=3D"font-size: 12pt; line-height: 150%; font-family: Courier; color: =
black;" lang=3D"EN-US">type specific informa</span></font><font color=3D"bl=
ack" size=3D"3" face=3D"Courier"><span style=3D"font-size: 12pt; line-heigh=
t: 150%; font-family: Courier; color: black;" lang=3D"EN-US">tion in i</spa=
n></font><font color=3D"black" size=3D"3" face=3D"Courier"><span style=3D"f=
ont-size: 12pt; line-height: 150%; font-family: Courier; color: black;" lan=
g=3D"EN-US">ts ICMPv6 message forma</span></font><font color=3D"black" size=
=3D"3" face=3D"Courier"><span style=3D"font-size: 12pt; line-height: 150%; =
font-family: Courier; color: black;" lang=3D"EN-US">t</span></font><font co=
lor=3D"black" size=3D"3" face=3D"Courier"><span style=3D"font-size: 12pt; l=
ine-height: 150%; font-family: Courier; color: black;" lang=3D"EN-US"></spa=
n></font><font color=3D"black" size=3D"3" face=3D"Courier"><span style=3D"f=
ont-size: 12pt; line-height: 150%; font-family: Courier; color: black;" lan=
g=3D"EN-US">.</span></font></p>
<p style=3D"margin-left: 0cm; line-height: 12pt;"><font color=3D"black" siz=
e=3D"3" face=3D"Courier"><span style=3D"font-size: 12pt; line-height: 150%;=
 font-family: Courier; color: black;" lang=3D"EN-US">Wi</span></font><font =
color=3D"black" size=3D"3" face=3D"Courier"><span style=3D"font-size: 12pt;=
 line-height: 150%; font-family: Courier; color: black;" lang=3D"EN-US">th =
regards,</span></font></p>
<p style=3D"margin-left: 0cm; line-height: 12pt;"><font color=3D"black" siz=
e=3D"3" face=3D"Courier"><span style=3D"font-size: 12pt; line-height: 150%;=
 font-family: Courier; color: black;" lang=3D"EN-US">Prejee</span></font><f=
ont color=3D"black" size=3D"3" face=3D"Courier"><span style=3D"font-size: 1=
2pt; line-height: 150%; font-family: Courier; color: black;" lang=3D"EN-US"=
>th.K</span></font></p>


------=_Part_179068_2242004.1230985750459--

--===============0973544040==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0973544040==--


From ipv6-bounces@ietf.org  Mon Jan  5 07:31:14 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 81EB33A6864;
	Mon,  5 Jan 2009 07:31:14 -0800 (PST)
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 62C5528C0E8
	for <ipv6@core3.amsl.com>; Mon,  5 Jan 2009 07:31:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.569
X-Spam-Level: 
X-Spam-Status: No, score=-6.569 tagged_above=-999 required=5 tests=[AWL=0.030, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 QZ43QFC8RW1H for <ipv6@core3.amsl.com>;
	Mon,  5 Jan 2009 07:31:12 -0800 (PST)
Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9])
	by core3.amsl.com (Postfix) with ESMTP id 951D628C0E7
	for <ipv6@ietf.org>; Mon,  5 Jan 2009 07:31:12 -0800 (PST)
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se
	[138.85.77.51])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id n05FZb2v015205;
	Mon, 5 Jan 2009 09:35:37 -0600
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.50]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 09:30:57 -0600
Received: from [142.133.10.113] ([142.133.10.113]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 5 Jan 2009 09:30:56 -0600
Message-ID: <49622813.9070301@ericsson.com>
Date: Mon, 05 Jan 2009 10:32:35 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Peter.Hunt@nokia.com
Subject: Re: DAD failure for global IPv6 addresses?
References: <808F2ECE7425024994976AC3D44BDCF4C8B8C4@vaebe108.NOE.Nokia.com>
In-Reply-To: <808F2ECE7425024994976AC3D44BDCF4C8B8C4@vaebe108.NOE.Nokia.com>
X-OriginalArrivalTime: 05 Jan 2009 15:30:56.0887 (UTC)
	FILETIME=[9A9AD070:01C96F4A]
Cc: 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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Hi Peter,
   There are really two questions hidden in your question.

Peter.Hunt@nokia.com wrote:
> All,
>  
> I have a question about what the correct behaviour should be for a 
> router if a global address fails DAD.
>  
> Specifically, if an interface has a link-local address which passes DAD, 
> but also has a global address configured which is not based on the 
> hardware address, and which fails DAD, what packets should be allowed 
> in/out of the interface?

If the global address fails DAD, it should not be configured on the 
interface. i.e. The only IPv6 address configured on the interface will 
be the link local address.

>  
> Should the system behave exactly as though the global address was 
> absent? That is, should the router forward packets to or from the failed 
> address/network based on whatever routes exist in the forwarding table?

Routing and forwarding decisions are completely independent of what 
addresses are configured on the interface. Contrary to IPv4 behavior, 
the configuration of an address using P::/64 prefix does not 
automatically add a route to the P::/64 prefix. What prefixes are 
on-link is determined by

a) on a router - by configuration
b) on a host - by information contained in the RAs

This means that you can add a route pointing to the right interface for 
the P::/64 prefix even if DAD failed for an address configured using 
this prefix on the same interface.

Cheers
Suresh

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


From ipv6-bounces@ietf.org  Mon Jan  5 09:47:23 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 361573A689E;
	Mon,  5 Jan 2009 09:47:23 -0800 (PST)
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 6AFF83A686B
	for <ipv6@core3.amsl.com>; Mon,  5 Jan 2009 09:22:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033, 
	BAYES_00=-2.599]
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 tycMNv3qmq-c for <ipv6@core3.amsl.com>;
	Mon,  5 Jan 2009 09:22:35 -0800 (PST)
Received: from jhuapl.edu (pilot.jhuapl.edu [128.244.198.200])
	by core3.amsl.com (Postfix) with ESMTP id 648F83A677E
	for <ipv6@ietf.org>; Mon,  5 Jan 2009 09:22:35 -0800 (PST)
Received: from ([128.244.206.11])
	by pilot.jhuapl.edu with ESMTP with TLS id 5502123.130723260;
	Mon, 05 Jan 2009 12:22:08 -0500
Message-ID: <496241C0.2040400@innovationslab.net>
Date: Mon, 05 Jan 2009 12:22:08 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: "Dunn, Jeffrey H." <jdunn@mitre.org>
Subject: Re: Protocol Action: 'Reserved IPv6 Interface Identifiers' to	Proposed
	Standard
References: <20081212175407.328433A6B08@core3.amsl.com>	<0AC4B700F00DBB4C94F95727E09914140161872E@IMCSRV7.MITRE.ORG>
	<4943212E.6020300@gmail.com> <49440BCD.50405@piuha.net>
	<0AC4B700F00DBB4C94F95727E09914140161873B@IMCSRV7.MITRE.ORG>
In-Reply-To: <0AC4B700F00DBB4C94F95727E09914140161873B@IMCSRV7.MITRE.ORG>
X-Mailman-Approved-At: Mon, 05 Jan 2009 09:47:22 -0800
Cc: 6man mailing list <ipv6@ietf.org>, Bob Hinden <bob.hinden@nokia.com>
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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Jeff,
      I do not see a consensus for making that type of change in the 
IPv6 Addressing Architecture.  I believe that the follow-up comments 
discussing how embedded the 64-bit boundary is are quite telling.

Regards,
Brian

Dunn, Jeffrey H. wrote:
> Jari and Brian,
> 
> Would the 6man group consider an update to RFC 4291 that is contains
> less prescriptive language? If so, I would be happy to undertake that
> task.  Please let me know.
> 
> Best Regards, 
>   
> Jeffrey Dunn 
> Info Systems Eng., Lead 
> MITRE Corporation.
> (301) 448-6965 (mobile)
> 
> -----Original Message-----
> From: Jari Arkko [mailto:jari.arkko@piuha.net] 
> Sent: Saturday, December 13, 2008 2:24 PM
> To: Brian E Carpenter
> Cc: Dunn, Jeffrey H.; Steve_Eiserman@ao.uscourts.gov; Internet
> Architecture Board; 6man mailing list; IESG; RFC Editor
> Subject: Re: Protocol Action: 'Reserved IPv6 Interface Identifiers' to
> Proposed Standard
> 
> Brian, Jeffrey,
> 
> The picture and text that you quoted are in this RFC exactly as they
> are 
> in RFC 4291. We did get some feedback on that text during the last
> call, 
> but we decided that it would be confusing for this particular RFC to
> say 
> something else than RFC 4291. RFC 4291 is, after all, the currently 
> approved addressing architecture document.
> 
> If we ever decide to make a change in the addressing architecture, we 
> should issue an RFC 4291bis, not change the text in the various other 
> RFCs that quote 4291 for some reason.
> 
> Jari
> 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


From ipv6-bounces@ietf.org  Mon Jan  5 11:49:25 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C84CB3A68E1;
	Mon,  5 Jan 2009 11:49:25 -0800 (PST)
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 E09033A68E1
	for <ipv6@core3.amsl.com>; Mon,  5 Jan 2009 11:49:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.202
X-Spam-Level: 
X-Spam-Status: No, score=-5.202 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396,
	RCVD_IN_DNSWL_MED=-4]
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 3y8-BSQrQaeq for <ipv6@core3.amsl.com>;
	Mon,  5 Jan 2009 11:49:24 -0800 (PST)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id A40F43A66B4
	for <ipv6@ietf.org>; Mon,  5 Jan 2009 11:49:23 -0800 (PST)
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	n05Jn72v027528; Mon, 5 Jan 2009 21:49:08 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 Jan 2009 21:49:07 +0200
Received: from vaebe108.NOE.Nokia.com ([10.160.244.69]) by
	esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 5 Jan 2009 21:49:07 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: DAD failure for global IPv6 addresses?
Date: Mon, 5 Jan 2009 21:46:23 +0200
Message-ID: <808F2ECE7425024994976AC3D44BDCF4C8B8CA@vaebe108.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: DAD failure for global IPv6 addresses?
thread-index: AclvSp88j/IUV9gOTnOOkihZBI6PZgAI6qBl
References: <808F2ECE7425024994976AC3D44BDCF4C8B8C4@vaebe108.NOE.Nokia.com>
	<49622813.9070301@ericsson.com>
From: <Peter.Hunt@nokia.com>
To: <suresh.krishnan@ericsson.com>
X-OriginalArrivalTime: 05 Jan 2009 19:49:07.0139 (UTC)
	FILETIME=[AB83B130:01C96F6E]
X-Nokia-AV: Clean
Cc: 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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0049319837=="
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0049319837==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C96F6E.AB512626"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C96F6E.AB512626
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Suresh,
=20
okay, that's very clear.
=20
Thanks,
Peter

________________________________

From: ext Suresh Krishnan [mailto:suresh.krishnan@ericsson.com]
Sent: Mon 1/5/2009 7:32 AM
To: Hunt Peter (Nokia-S/MtView)
Cc: ipv6@ietf.org
Subject: Re: DAD failure for global IPv6 addresses?



Hi Peter,
   There are really two questions hidden in your question.

Peter.Hunt@nokia.com wrote:
> All,
>=20
> I have a question about what the correct behaviour should be for a
> router if a global address fails DAD.
>=20
> Specifically, if an interface has a link-local address which passes =
DAD,
> but also has a global address configured which is not based on the
> hardware address, and which fails DAD, what packets should be allowed
> in/out of the interface?

If the global address fails DAD, it should not be configured on the
interface. i.e. The only IPv6 address configured on the interface will
be the link local address.

>=20
> Should the system behave exactly as though the global address was
> absent? That is, should the router forward packets to or from the =
failed
> address/network based on whatever routes exist in the forwarding =
table?

Routing and forwarding decisions are completely independent of what
addresses are configured on the interface. Contrary to IPv4 behavior,
the configuration of an address using P::/64 prefix does not
automatically add a route to the P::/64 prefix. What prefixes are
on-link is determined by

a) on a router - by configuration
b) on a host - by information contained in the RAs

This means that you can add a route pointing to the right interface for
the P::/64 prefix even if DAD failed for an address configured using
this prefix on the same interface.

Cheers
Suresh




------_=_NextPart_001_01C96F6E.AB512626
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Re: DAD failure for global IPv6 =
addresses?</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.6001.18183" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText55026 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" color=3D#000000 =
size=3D2>Suresh,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>okay, that's very =
clear.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>Thanks,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" =
size=3D2>Peter</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> ext Suresh Krishnan =
[mailto:suresh.krishnan@ericsson.com]<BR><B>Sent:</B> Mon 1/5/2009 7:32 =
AM<BR><B>To:</B> Hunt Peter (Nokia-S/MtView)<BR><B>Cc:</B> =
ipv6@ietf.org<BR><B>Subject:</B> Re: DAD failure for global IPv6 =
addresses?<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>Hi Peter,<BR>&nbsp;&nbsp; There are really two =
questions hidden in your question.<BR><BR>Peter.Hunt@nokia.com =
wrote:<BR>&gt; All,<BR>&gt;&nbsp;<BR>&gt; I have a question about what =
the correct behaviour should be for a<BR>&gt; router if a global address =
fails DAD.<BR>&gt;&nbsp;<BR>&gt; Specifically, if an interface has a =
link-local address which passes DAD,<BR>&gt; but also has a global =
address configured which is not based on the<BR>&gt; hardware address, =
and which fails DAD, what packets should be allowed<BR>&gt; in/out of =
the interface?<BR><BR>If the global address fails DAD, it should not be =
configured on the<BR>interface. i.e. The only IPv6 address configured on =
the interface will<BR>be the link local =
address.<BR><BR>&gt;&nbsp;<BR>&gt; Should the system behave exactly as =
though the global address was<BR>&gt; absent? That is, should the router =
forward packets to or from the failed<BR>&gt; address/network based on =
whatever routes exist in the forwarding table?<BR><BR>Routing and =
forwarding decisions are completely independent of what<BR>addresses are =
configured on the interface. Contrary to IPv4 behavior,<BR>the =
configuration of an address using P::/64 prefix does =
not<BR>automatically add a route to the P::/64 prefix. What prefixes =
are<BR>on-link is determined by<BR><BR>a) on a router - by =
configuration<BR>b) on a host - by information contained in the =
RAs<BR><BR>This means that you can add a route pointing to the right =
interface for<BR>the P::/64 prefix even if DAD failed for an address =
configured using<BR>this prefix on the same =
interface.<BR><BR>Cheers<BR>Suresh<BR><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C96F6E.AB512626--

--===============0049319837==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0049319837==--


From ipv6-bounces@ietf.org  Wed Jan  7 01:24:08 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0BC803A6A37;
	Wed,  7 Jan 2009 01:24:08 -0800 (PST)
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 2901F3A6A32
	for <ipv6@core3.amsl.com>; Wed,  7 Jan 2009 01:24:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 OF8AmzPYaPr2 for <ipv6@core3.amsl.com>;
	Wed,  7 Jan 2009 01:24:06 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33])
	by core3.amsl.com (Postfix) with SMTP id D814C3A6A37
	for <ipv6@ietf.org>; Wed,  7 Jan 2009 01:24:05 -0800 (PST)
Received: (qmail 51442 invoked from network); 7 Jan 2009 08:23:47 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33)
	by bizet.nethelp.no with SMTP; 7 Jan 2009 08:23:47 -0000
Date: Wed, 07 Jan 2009 09:23:47 +0100 (CET)
Message-Id: <20090107.092347.74702282.sthaug@nethelp.no>
To: suresh.krishnan@ericsson.com
Subject: Re: DAD failure for global IPv6 addresses?
From: sthaug@nethelp.no
In-Reply-To: <808F2ECE7425024994976AC3D44BDCF4C8B8CA@vaebe108.NOE.Nokia.com>
References: <808F2ECE7425024994976AC3D44BDCF4C8B8C4@vaebe108.NOE.Nokia.com>
	<49622813.9070301@ericsson.com>
	<808F2ECE7425024994976AC3D44BDCF4C8B8CA@vaebe108.NOE.Nokia.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Cc: 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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

> Routing and forwarding decisions are completely independent of what
> addresses are configured on the interface. Contrary to IPv4 behavior,
> the configuration of an address using P::/64 prefix does not
> automatically add a route to the P::/64 prefix. What prefixes are
> on-link is determined by
> 
> a) on a router - by configuration
> b) on a host - by information contained in the RAs

It may be sacrilege to mention it in this group - but b) here is
certainly not the only view of how things work (or for that matter
how they *should* work). For instance - FreeBSD 7.x needs explicit
configuration to turn on IPv6. If IPv6 is turned on, you can configure
a static IPv6 address (for instance a /64 prefix) for an interface -
and this will indeed add a route to this /64 network. Or you can use
various types of autoconfiguration.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


From ipv6-bounces@ietf.org  Wed Jan  7 17:07:31 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9FF533A6A96;
	Wed,  7 Jan 2009 17:07:31 -0800 (PST)
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 591153A68A6
	for <ipv6@core3.amsl.com>; Wed,  7 Jan 2009 17:07:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.6
X-Spam-Level: 
X-Spam-Status: No, score=0.6 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, NO_RELAYS=-0.001]
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 5+X6I2HN99Ar for <ipv6@core3.amsl.com>;
	Wed,  7 Jan 2009 17:07:29 -0800 (PST)
Received: from mon.jinmei.org (mon.jinmei.org [IPv6:2001:4f8:3:36::162])
	by core3.amsl.com (Postfix) with ESMTP id A2D393A6A9B
	for <ipv6@ietf.org>; Wed,  7 Jan 2009 17:07:28 -0800 (PST)
Received: from jmb.jinmei.org (unknown [IPv6:2001:4f8:3:bb:217:f2ff:fee0:a91f])
	by mon.jinmei.org (Postfix) with ESMTP id EB46D33C2E;
	Wed,  7 Jan 2009 17:07:13 -0800 (PST)
Date: Wed, 07 Jan 2009 17:07:13 -0800
Message-ID: <m2bpui4ncu.wl%Jinmei_Tatuya@isc.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<Jinmei_Tatuya@isc.org>
To: sthaug@nethelp.no
Subject: Re: DAD failure for global IPv6 addresses?
In-Reply-To: <20090107.092347.74702282.sthaug@nethelp.no>
References: <808F2ECE7425024994976AC3D44BDCF4C8B8C4@vaebe108.NOE.Nokia.com>
	<49622813.9070301@ericsson.com>
	<808F2ECE7425024994976AC3D44BDCF4C8B8CA@vaebe108.NOE.Nokia.com>
	<20090107.092347.74702282.sthaug@nethelp.no>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.1 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Cc: ipv6@ietf.org, suresh.krishnan@ericsson.com
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

At Wed, 07 Jan 2009 09:23:47 +0100 (CET),
sthaug@nethelp.no wrote:

> > Routing and forwarding decisions are completely independent of what
> > addresses are configured on the interface. Contrary to IPv4 behavior,
> > the configuration of an address using P::/64 prefix does not
> > automatically add a route to the P::/64 prefix. What prefixes are
> > on-link is determined by
> > 
> > a) on a router - by configuration
> > b) on a host - by information contained in the RAs
> 
> It may be sacrilege to mention it in this group - but b) here is
> certainly not the only view of how things work (or for that matter
> how they *should* work). For instance - FreeBSD 7.x needs explicit
> configuration to turn on IPv6. If IPv6 is turned on, you can configure
> a static IPv6 address (for instance a /64 prefix) for an interface -
> and this will indeed add a route to this /64 network. Or you can use
> various types of autoconfiguration.

As you seem to indicate, this should rather be considered an
implementation details, but this FreeBSD's behavior should be viewed
as a shortcut of configuring both an address and an on-link prefix by
a single operation, rather than an instance that "configuring an
address automatically adds a route to the /64 prefix" (I know that,
because I designed and implemented it:-).  In fact, the FreeBSD kernel
internally maintains addresses and prefixes separately, and in that
sense it rather diligently follows the model that Suresh explained.
It adopts the "shortcut" behavior as a compromise for existing
operators who are very familiar with IPv4 operations and would expect
the same side effect.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


From ipv6-bounces@ietf.org  Thu Jan 15 12:06:24 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C8873A68B1;
	Thu, 15 Jan 2009 12:06:24 -0800 (PST)
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 366E63A68B1
	for <ipv6@core3.amsl.com>; Thu, 15 Jan 2009 12:06:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.727
X-Spam-Level: 
X-Spam-Status: No, score=-6.727 tagged_above=-999 required=5
	tests=[AWL=-0.128, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 7e9lNdnwWv8S for <ipv6@core3.amsl.com>;
	Thu, 15 Jan 2009 12:06:22 -0800 (PST)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233])
	by core3.amsl.com (Postfix) with ESMTP id 6B62A3A6783
	for <ipv6@ietf.org>; Thu, 15 Jan 2009 12:06:18 -0800 (PST)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com
	[10.160.244.31])
	by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	n0FK60Ij014805; Thu, 15 Jan 2009 22:06:01 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 15 Jan 2009 22:05:58 +0200
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by
	esebh102.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.3959); Thu, 15 Jan 2009 22:05:57 +0200
Received: from dadhcp-172019074149.americas.nokia.com
	(dadhcp-172019074149.americas.nokia.com [172.19.74.149])
	by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	n0FK5svP021923; Thu, 15 Jan 2009 22:05:55 +0200
Message-Id: <AD36E02A-0254-415F-9553-331FB1172B08@nokia.com>
From: Bob Hinden <bob.hinden@nokia.com>
To: IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Call for Agenda Items for IETF74 in San Francisco
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 15 Jan 2009 12:05:53 -0800
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 15 Jan 2009 20:05:57.0569 (UTC)
	FILETIME=[ADE89310:01C9774C]
X-Nokia-AV: Clean
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bob.hinden@nokia.com
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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Hi,

The chairs would like to solicit proposals for agenda items for a 6MAN  
session at IETF74 before requesting a meeting slot.  We will give  
priority to working group items.  We would like to hear from the  
authors of current working group drafts.

Thanks,

Bob Hinden & Brian Haberman


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


From ipv6-bounces@ietf.org  Fri Jan 16 02:58:16 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E1C5C3A6A45;
	Fri, 16 Jan 2009 02:58:15 -0800 (PST)
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 AC76B3A6A45
	for <ipv6@core3.amsl.com>; Fri, 16 Jan 2009 02:58:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.765
X-Spam-Level: 
X-Spam-Status: No, score=0.765 tagged_above=-999 required=5 tests=[AWL=0.763, 
	BAYES_50=0.001, HTML_MESSAGE=0.001]
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 SNewiEUgNNxm for <ipv6@core3.amsl.com>;
	Fri, 16 Jan 2009 02:58:13 -0800 (PST)
Received: from web35307.mail.mud.yahoo.com (web35307.mail.mud.yahoo.com
	[66.163.179.101])
	by core3.amsl.com (Postfix) with SMTP id 473F33A6872
	for <ipv6@ietf.org>; Fri, 16 Jan 2009 02:58:13 -0800 (PST)
Received: (qmail 55729 invoked by uid 60001); 16 Jan 2009 10:57:58 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=ckdJY/2tSaB3QG1nXDTu+AWN5CVxPVUEGbdUy3zpmL398brUhmwAscgupzKTFhs+5MJj4iNNoLxy2XiXU8cRURHsux4xy5LvsgUp7Zk4xU2kHXHA56n1kAMhOfaX9dPxHRnCF7CN5C6CcjZYcGQ4/ixGoC1/3w7oPjX+lf1yrKI=;
X-YMail-OSG: IOb6JzcVM1kJMWKVuJWu28FjbnfNstfqA4t6B3RH7LykGaZvoOLRFaPWYtHTDjHUIVAcgjtlfOZAJQzgVvrmmS3fG8iLBWQu9TrRmMJ0Qt0wa0mzB2bpMSEaJvuq8y9QFlEVByhCmAK.zXdGysG7MphZZMvykJv1gaHkh3eWbcrkd6tjwclgsELkyc7KAu_oPBplXvXwCMXaL6ONK08A25lMtiSAo9A874gY
Received: from [94.249.25.221] by web35307.mail.mud.yahoo.com via HTTP;
	Fri, 16 Jan 2009 02:57:58 PST
X-Mailer: YahooMailWebService/0.7.260.1
Date: Fri, 16 Jan 2009 02:57:58 -0800 (PST)
From: Alaa Al-Din Al-Radhi <alradhi2000@yahoo.ca>
Subject: Cisco 2008 Annual Security Report
To: ipv6@ietf.org
MIME-Version: 1.0
Message-ID: <109533.54061.qm@web35307.mail.mud.yahoo.com>
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============2136878696=="
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

--===============2136878696==
Content-Type: multipart/alternative; boundary="0-1351241830-1232103478=:54061"

--0-1351241830-1232103478=:54061
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Colleagues
=A0
A very good resource to read
=A0
http://cisco.com/en/US/prod/vpndevc/annual_security_report.html
=A0
Alaa=0A=0A=0A      ________________________________________________________=
__________=0AInstant Messaging, free SMS, sharing photos and more... Try th=
e new Yahoo! Canada Messenger at http://ca.beta.messenger.yahoo.com/
--0-1351241830-1232103478=:54061
Content-Type: text/html; charset=us-ascii

<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><DIV>Dear Colleagues</DIV>
<DIV>&nbsp;</DIV>
<DIV>A very good resource to read</DIV>
<DIV>&nbsp;</DIV>
<DIV><A href="http://cisco.com/en/US/prod/vpndevc/annual_security_report.html" target=_blank rel=nofollow>http://cisco.com/en/US/prod/vpndevc/annual_security_report.html</A></DIV>
<DIV>&nbsp;</DIV>
<DIV>Alaa</DIV></td></tr></table><br>
      <hr size=1>
Looking for the perfect gift?<a href="http://www.flickr.com/gift/"><b> Give the gift of Flickr!</b></a>
--0-1351241830-1232103478=:54061--

--===============2136878696==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============2136878696==--


From ipv6-bounces@ietf.org  Sun Jan 18 01:21:30 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1022C3A6879;
	Sun, 18 Jan 2009 01:21:30 -0800 (PST)
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 069E93A68D1
	for <ipv6@core3.amsl.com>; Sun, 18 Jan 2009 01:21:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.077
X-Spam-Level: 
X-Spam-Status: No, score=0.077 tagged_above=-999 required=5 tests=[AWL=-0.923, 
	BAYES_60=1, HTML_MESSAGE=0.001]
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 RJAqkYmr3+be for <ipv6@core3.amsl.com>;
	Sun, 18 Jan 2009 01:21:28 -0800 (PST)
Received: from web35308.mail.mud.yahoo.com (web35308.mail.mud.yahoo.com
	[66.163.179.102])
	by core3.amsl.com (Postfix) with SMTP id 3AC023A6879
	for <ipv6@ietf.org>; Sun, 18 Jan 2009 01:21:28 -0800 (PST)
Received: (qmail 17239 invoked by uid 60001); 18 Jan 2009 09:21:11 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=vq4MbvYxfsN+UVqOxfq9wf+EOJUzPaqEfiQ+Pw9saa442B6aupbNaZbZqq1Hyq2zncdyxBZWHRqRwHTdQAauMFlSamkL8WoJkjSs5jhnXpnFZHpVwgOsRixyHMQrkmvprEbzcly8R6VkgPnKplYwZgdvOJc2jCPs9kK5np9CNqc=;
X-YMail-OSG: jsqO8c8VM1nswMLWz7iGzCdFeRVaCtltpKtCLhoMTkdBluHIzSVRLDEiWQqV_qLIZuQdNRMaSXfewF07mdYfpkAm8mllXxfzaeFDWJPtUbJ9jt1JNFgbD6yOAKvvFTubElPbN_Enyhst1JNeLYbEn_ONkBTvNWZx.6HjKrs.6SkKqhFekRV7kZvvP2LPAcuiKhqgFC2PFcB2slMKW8HQW4AJGSXfA_ewxwJh_ty6tLTuAEQ_bzLdCWNhcQ--
Received: from [79.173.250.240] by web35308.mail.mud.yahoo.com via HTTP;
	Sun, 18 Jan 2009 01:21:11 PST
X-Mailer: YahooMailWebService/0.7.260.1
Date: Sun, 18 Jan 2009 01:21:11 -0800 (PST)
From: Alaa Al-Din Al-Radhi <alradhi2000@yahoo.ca>
Subject: IPv6 Latest Report 2009
To: ipv6@ietf.org
MIME-Version: 1.0
Message-ID: <933619.16336.qm@web35308.mail.mud.yahoo.com>
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0230335335=="
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

--===============0230335335==
Content-Type: multipart/alternative; boundary="0-383494471-1232270471=:16336"

--0-383494471-1232270471=:16336
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Colleagues
=A0
A new report on IPv6. May be you find it interesting
=A0
http://tinyurl.com/7q8kbw
=A0
Alaa=0A=0A=0A      ________________________________________________________=
__________=0AInstant Messaging, free SMS, sharing photos and more... Try th=
e new Yahoo! Canada Messenger at http://ca.beta.messenger.yahoo.com/
--0-383494471-1232270471=:16336
Content-Type: text/html; charset=us-ascii

<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><DIV>Dear Colleagues</DIV>
<DIV>&nbsp;</DIV>
<DIV>A new report on IPv6. May be you find it interesting</DIV>
<DIV>&nbsp;</DIV>
<DIV><A href="http://tinyurl.com/7q8kbw" target=_blank rel=nofollow>http://tinyurl.com/7q8kbw</A></DIV>
<DIV>&nbsp;</DIV>
<DIV>Alaa</DIV></td></tr></table><br>



      <hr size=1>Now with a new friend-happy design! Try the new <a href="http://ca.beta.messenger.yahoo.com/"><b>Yahoo! Canada Messenger</b></a>
--0-383494471-1232270471=:16336--

--===============0230335335==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0230335335==--


From ipv6-bounces@ietf.org  Tue Jan 20 10:24:39 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7BFFC3A6A05;
	Tue, 20 Jan 2009 10:24:39 -0800 (PST)
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 874793A690D
	for <ipv6@core3.amsl.com>; Tue, 20 Jan 2009 10:24:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
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 KQjq21j2FFlk for <ipv6@core3.amsl.com>;
	Tue, 20 Jan 2009 10:24:15 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140])
	by core3.amsl.com (Postfix) with ESMTP id BADFF3A6878
	for <ipv6@ietf.org>; Tue, 20 Jan 2009 10:24:15 -0800 (PST)
Received: from localhost (localhost.fuaim.com [127.0.0.1])
	by uillean.fuaim.com (Postfix) with ESMTP id 4B358B8A7;
	Tue, 20 Jan 2009 10:23:53 -0800 (PST)
Received: from uillean.fuaim.com ([127.0.0.1])
	by localhost (uillean.fuaim.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id ylH8xObOYfxF; Tue, 20 Jan 2009 10:23:52 -0800 (PST)
Received: from clairseach.fuaim.com (unknown
	[IPv6:2001:470:117:128:20c:29ff:fe3c:1706])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by uillean.fuaim.com (Postfix) with ESMTP id DC5A9B8B3;
	Tue, 20 Jan 2009 10:23:51 -0800 (PST)
Received: from Clemson.local (c-76-100-31-131.hsd1.md.comcast.net
	[76.100.31.131]) (authenticated bits=0)
	by clairseach.fuaim.com (8.12.8/8.12.8) with ESMTP id n0KI83J9017671;
	Tue, 20 Jan 2009 10:08:03 -0800
Message-ID: <497616AC.6070000@innovationslab.net>
Date: Tue, 20 Jan 2009 13:23:40 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
MIME-Version: 1.0
To: IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: Call for Agenda Items for IETF74 in San Francisco
References: <AD36E02A-0254-415F-9553-331FB1172B08@nokia.com>
In-Reply-To: <AD36E02A-0254-415F-9553-331FB1172B08@nokia.com>
X-Mailman-Approved-At: Tue, 20 Jan 2009 10:24:38 -0800
Cc: bob.hinden@nokia.com
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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

All,
      This is a reminder that the chairs request input on proposed
discussion topics for the upcoming meeting in San Francisco.  We need
input by 9:00AM PST on January 21, 2009.

Regards,
Brian & Bob

Bob Hinden wrote:
> Hi,
> 
> The chairs would like to solicit proposals for agenda items for a 6MAN 
> session at IETF74 before requesting a meeting slot.  We will give 
> priority to working group items.  We would like to hear from the authors 
> of current working group drafts.
> 
> Thanks,
> 
> Bob Hinden & Brian Haberman
> 


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



From ipv6-bounces@ietf.org  Tue Jan 20 14:15:25 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C86D3A6A1A; Tue, 20 Jan 2009 14:15:25 -0800 (PST)
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 9978C3A6A13 for <ipv6@core3.amsl.com>; Tue, 20 Jan 2009 14:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
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 QBzmQXjRsYSc for <ipv6@core3.amsl.com>; Tue, 20 Jan 2009 14:15:22 -0800 (PST)
Received: from prometheus.interunix.net (prometheus.interunix.net [202.190.74.58]) by core3.amsl.com (Postfix) with SMTP id 9A6043A688B for <ipv6@ietf.org>; Tue, 20 Jan 2009 14:15:20 -0800 (PST)
Received: (qmail 98492 invoked by uid 1012); 20 Jan 2009 22:15:00 -0000
Received: from 202.190.74.58 by prometheus.interunix.net (envelope-from <prabu@hackinthebox.org>, uid 1010) with qmail-scanner-1.25-st-qms  (clamdscan: 0.87/3227. spamassassin: 3.1.8. perlscan: 1.25-st-qms.   Clear:RC:0(202.190.74.58):SA:0(-4.4/5.0):.  Processed in 1.044963 secs); 20 Jan 2009 22:15:00 -0000
X-Antivirus-INTERUNIX-Mail-From: prabu@hackinthebox.org via prometheus.interunix.net
X-Antivirus-INTERUNIX: 1.25-st-qms (Clear:RC:0(202.190.74.58):SA:0(-4.4/5.0):. Processed in 1.044963 secs Process 98477)
Received: from unknown (HELO ?192.168.1.33?) (prabu@hackinthebox.org@202.190.74.58) by prometheus.interunix.net with SMTP; 20 Jan 2009 22:14:59 -0000
Message-ID: <49764CCF.8020604@hackinthebox.org>
Date: Wed, 21 Jan 2009 06:14:39 +0800
From: Praburaajan <prabu@hackinthebox.org>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: ipv6@ietf.org, asterisk-security@lists.digium.com,  asterisk-users@lists.digium.com, bugtraq@securityfocus.com
Subject: Videos from HITBSecConf2008  - Malaysia released!
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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org The videos from HITBSecConf2008 - Malaysia are now available for download!

Day 1
=====

http://thepiratebay.org/torrent/4654588/HITBSecConf2008_-_Malaysia_Videos___Day_1
	
Keynote Address 1: The Art of Click-Jacking - Jeremiah Grossman
Keynote Address 2: Cyberwar is Bullshit - Marcus Ranum

Presentations:

- Delivering Identity Management 2.0 by Leveraging OPSS
- Bluepilling the Xen Hypervisor
- Pass the Hash Toolkit for Windows
- Internet Explorer 8 - Trustworthy Engineering and Browsing
- Full Process Reconsitution from Memory
- Hacking Internet Kiosks
- Analysis and Visualization of Common Packers
- A Fox in the Hen House - UPnP IGD
- MoocherHunting
- Browser Exploits: A New Model for Browser Security
- Time for a Free Hardware Foundation?
- Mac OS Xploitation
- Hacking a Bird in The Sky 2.0
- How the Leopard Hides His Spots - OS X Anti-Forensics Techniques


Day 2
=====

http://thepiratebay.org/torrent/4654974/HITBSecConf2008_-_Malaysia_Videos___Day_2

Keynote Address 3:  Dissolving an Industry as a Hobby - THE PIRATE BAY

Presentations:

- Pushing the Camel Through the Eye of a Needle
- An Effective Methodology to Enable Security Evaluation at RTL Level
- Remote Code Execution Through Intel CPU Bugs
- Next Generation Reverse Shell
- Build Your Own Password Cracker with a Disassembler and VM Magic
- Decompilers and Beyond
- Cracking into Embedded Devices and Beyond!
- Client-side Security
- Top 10 Web 2.0 Attacks

===

On a related note, the registration for HITBSecConf2009 - Dubai (20th -
23rd April) is now open!

http://conference.hitb.org/hitbsecconf2009dubai/

The Call for Papers (CFP) for HITBSecConf2009 - Malaysia (October 5th -
8th) will open in March 2009.

A belated Happy New Year from all of us at Hack in The Box and may all
your exploits result in root shell!  :)

The HITB Team.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Tue Jan 20 21:35:49 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DB603A6A1C; Tue, 20 Jan 2009 21:35:49 -0800 (PST)
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 6DABA3A6A1C for <ipv6@core3.amsl.com>; Tue, 20 Jan 2009 21:35:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.52
X-Spam-Level: 
X-Spam-Status: No, score=-110.52 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 LFBz67vL-v88 for <ipv6@core3.amsl.com>; Tue, 20 Jan 2009 21:35:47 -0800 (PST)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 95DB23A6955 for <ipv6@ietf.org>; Tue, 20 Jan 2009 21:35:47 -0800 (PST)
Received: from TK5-EXHUB-C102.redmond.corp.microsoft.com (157.54.18.53) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.1.291.1; Tue, 20 Jan 2009 21:37:04 -0800
Received: from tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com (157.54.18.33) by TK5-EXHUB-C102.redmond.corp.microsoft.com (157.54.18.53) with Microsoft SMTP Server id 8.1.340.0; Tue, 20 Jan 2009 21:35:31 -0800
Received: from NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com ([fe80::8de9:51a2:cd62:f122]) by tk5-exmlt-w602.wingroup.windeploy.ntdev.microsoft.com ([157.54.18.33]) with mapi; Tue, 20 Jan 2009 21:35:31 -0800
From: Christian Huitema <huitema@windows.microsoft.com>
To: 6man <ipv6@ietf.org>
Date: Tue, 20 Jan 2009 21:35:28 -0800
Subject: Standard status of RFC 3879
Thread-Topic: Standard status of RFC 3879
Thread-Index: Acl7ihGPu646J57yROat60dKoZ7GJQ==
Message-ID: <8EFB68EAE061884A8517F2A755E8B60A19D3AB6593@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1845129649=="
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org --===============1845129649==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_8EFB68EAE061884A8517F2A755E8B60A19D3AB6593NAEXMSGW601wi_"

--_000_8EFB68EAE061884A8517F2A755E8B60A19D3AB6593NAEXMSGW601wi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

RFC 3879 was published as proposed standard about 5 years ago. Do we intend=
 to leave it at that stage, or to update its status along the standard trac=
k?

-- Christian Huitema


--_000_8EFB68EAE061884A8517F2A755E8B60A19D3AB6593NAEXMSGW601wi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:D=3D"DAV:" xmln=
s:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois=3D"ht=
tp://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://schema=
s.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3.org/2=
000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http://www=
.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sharepoin=
t/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" xmlns=
:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://schema=
s.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSc=
hema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" xm=
lns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p=3D=
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http://schem=
as.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://schemas.mi=
crosoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.microsof=
t.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformats.org/=
package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlformats=
.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.com/off=
ice/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/package/=
2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpa=
ges" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/typ=
es" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/mess=
ages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibr=
ary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer=
/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:st=3D"=
&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 face=3DCalibri><span style=3D'font-size=
:12.0pt'>RFC
3879 was published as proposed standard about 5 years ago. Do we intend to
leave it at that stage, or to update its status along the standard track?<o=
:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3DCalibri><span style=3D'font-size=
:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'>--
Christian Huitema<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--_000_8EFB68EAE061884A8517F2A755E8B60A19D3AB6593NAEXMSGW601wi_--

--===============1845129649==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1845129649==--

From ipv6-bounces@ietf.org  Wed Jan 21 03:31:48 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B81328C102; Wed, 21 Jan 2009 03:31:48 -0800 (PST)
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 CD0ED28C102 for <ipv6@core3.amsl.com>; Wed, 21 Jan 2009 03:31:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 jCsF0MN1uyf2 for <ipv6@core3.amsl.com>; Wed, 21 Jan 2009 03:31:47 -0800 (PST)
Received: from owl.ecs.soton.ac.uk (owl.ecs.soton.ac.uk [IPv6:2001:630:d0:f102:230:48ff:fe77:96e]) by core3.amsl.com (Postfix) with ESMTP id BBFAC28C0EC for <ipv6@ietf.org>; Wed, 21 Jan 2009 03:31:46 -0800 (PST)
X-ECS-MailScanner-Watermark: 1233142225.08864@qQKJh435GojxVC+0cs6miA
Received: from gander.ecs.soton.ac.uk ([IPv6:2001:630:d0:f102:21d:9ff:fe22:9fc]) by owl.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id n0LBUP2m002426; Wed, 21 Jan 2009 11:30:25 GMT
Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk [IPv6:2001:630:d0:f102:230:48ff:fe59:5f12]) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id n0LBVFUU026762 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jan 2009 11:31:15 GMT
Received: from login.ecs.soton.ac.uk (localhost.localdomain [127.0.0.1]) by login.ecs.soton.ac.uk (8.13.8/8.11.6) with ESMTP id n0LBVFQG021064;  Wed, 21 Jan 2009 11:31:15 GMT
Received: (from tjc@localhost) by login.ecs.soton.ac.uk (8.13.8/8.13.8/Submit) id n0LBVEQn021063; Wed, 21 Jan 2009 11:31:14 GMT
Date: Wed, 21 Jan 2009 11:31:14 +0000
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: Brian Haberman <brian@innovationslab.net>
Subject: Re: Call for Agenda Items for IETF74 in San Francisco
Message-ID: <20090121113114.GG19720@login.ecs.soton.ac.uk>
Mail-Followup-To: Brian Haberman <brian@innovationslab.net>, IPv6 WG Mailing List <ipv6@ietf.org>, bob.hinden@nokia.com
References: <AD36E02A-0254-415F-9553-331FB1172B08@nokia.com> <497616AC.6070000@innovationslab.net>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <497616AC.6070000@innovationslab.net>
User-Agent: Mutt/1.4.2.2i
X-ECS-MailScanner-ID: n0LBVFUU026762
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: n0LBUP2m002426
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: bob.hinden@nokia.com, 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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org Hi,

We'll need a slot for the Address Selection Design Team update, maybe
20 mins or so I'd guess.   Discussions have resumed on the team list
so a new draft will probably be out soon capturing that and feedback
from IETF73.

Tim

On Tue, Jan 20, 2009 at 01:23:40PM -0500, Brian Haberman wrote:
> All,
>      This is a reminder that the chairs request input on proposed
> discussion topics for the upcoming meeting in San Francisco.  We need
> input by 9:00AM PST on January 21, 2009.
> 
> Regards,
> Brian & Bob
> 
> Bob Hinden wrote:
> >Hi,
> >
> >The chairs would like to solicit proposals for agenda items for a 6MAN 
> >session at IETF74 before requesting a meeting slot.  We will give 
> >priority to working group items.  We would like to hear from the authors 
> >of current working group drafts.
> >
> >Thanks,
> >
> >Bob Hinden & Brian Haberman
> >
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

-- 
Tim


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Wed Jan 21 10:06:06 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 131BC3A6916; Wed, 21 Jan 2009 10:06:06 -0800 (PST)
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 77D453A6916 for <ipv6@core3.amsl.com>; Wed, 21 Jan 2009 10:06:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.706
X-Spam-Level: 
X-Spam-Status: No, score=-6.706 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 io6j3Rk71ADk for <ipv6@core3.amsl.com>; Wed, 21 Jan 2009 10:06:03 -0800 (PST)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 7B0123A67FA for <ipv6@ietf.org>; Wed, 21 Jan 2009 10:06:03 -0800 (PST)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n0LI5P5D001341; Wed, 21 Jan 2009 20:05:43 +0200
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 21 Jan 2009 20:05:40 +0200
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Wed, 21 Jan 2009 20:05:39 +0200
Received: from dadhcp-172019074205.americas.nokia.com (dadhcp-172019074205.americas.nokia.com [172.19.74.205]) by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id n0LI5Zu4009918; Wed, 21 Jan 2009 20:05:37 +0200
From: Bob Hinden <bob.hinden@nokia.com>
To: Christian Huitema <huitema@windows.microsoft.com>
In-Reply-To: <8EFB68EAE061884A8517F2A755E8B60A19D3AB6593@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
Subject: Re: Standard status of RFC 3879
References: <8EFB68EAE061884A8517F2A755E8B60A19D3AB6593@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
Message-Id: <E5653CB3-3296-4E32-BD83-658EE8343DC5@nokia.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 21 Jan 2009 10:05:36 -0800
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 21 Jan 2009 18:05:39.0971 (UTC) FILETIME=[DE5D0530:01C97BF2]
X-Nokia-AV: Clean
Cc: 6man <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bob.hinden@nokia.com
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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org Christian,

> RFC 3879 was published as proposed standard about 5 years ago. Do we  
> intend to leave it at that stage, or to update its status along the  
> standard track?
>

What did you have in mind?  Is there a reason to advance it?

Bob

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Wed Jan 21 10:56:46 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA2B828C102; Wed, 21 Jan 2009 10:56:46 -0800 (PST)
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 A948128C102; Wed, 21 Jan 2009 10:56:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.669
X-Spam-Level: 
X-Spam-Status: No, score=-5.669 tagged_above=-999 required=5 tests=[AWL=-0.930, BAYES_20=-0.74, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 3LWRYsIluPsj; Wed, 21 Jan 2009 10:56:42 -0800 (PST)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id A3C3F3A685D; Wed, 21 Jan 2009 10:56:41 -0800 (PST)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0LIuOxO005054;  Wed, 21 Jan 2009 13:56:24 -0500
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0LIuOgx005015;  Wed, 21 Jan 2009 13:56:24 -0500
Received: from IMCMBX1.MITRE.ORG ([129.83.29.204]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Wed, 21 Jan 2009 13:56:24 -0500
From: "Dunn, Jeffrey H." <jdunn@mitre.org>
To: "ipv6-bounces@ietf.org" <ipv6-bounces@ietf.org>, "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, 6man mailing list <ipv6@ietf.org>
Date: Wed, 21 Jan 2009 13:56:23 -0500
Subject: End System PMTUD behavior question
Thread-Topic: End System PMTUD behavior question
Thread-Index: Acl7+fSDtCRQmHdATNy7UebOW+92QA==
Message-ID: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "Sherman, Kurt T." <ksherman@mitre.org>, "Liou, Chern" <csliou@mitre.org>, "steve_eiserman@uscourts.gov" <steve_eiserman@uscourts.gov>, "Huang, Frank" <fhuang@mitre.org>, "Grayeli, Parisa" <pgrayeli@mitre.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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1783022297=="
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org --===============1783022297==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_3C6F21684E7C954193E6C7C4573B762701D3DD67DAIMCMBX1MITREO_"

--_000_3C6F21684E7C954193E6C7C4573B762701D3DD67DAIMCMBX1MITREO_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Colleagues,

We have been performing some PMTUD tests and have found that different oper=
ating systems handle PMTUD differently. Specifically, we found that the "pi=
ng" application behaves in the following way when the PMTU is set to 1280 a=
nd a 1500 octet ICMPv6 echo request is sent to that routed path. The hosts =
we tested:


1.      Send one or two un-fragmented echo requests

2.      Receive the "Packet Too Big" ICMPv6 message from the first interfac=
e with the 1280 octet MTU

3.      Begin to send echo requests in two fragments

The following questions occurred to us:


1.      Should the hosts re-transmit the ICMPv6 echo request(s) in fragment=
s?

2.      If not, should the host that sent two echo requests have waited for=
 a response in support of PMTUD?

Any assistance you can provide, especially commercial specification for shi=
pping product or other applications, would be most helpful. Many thanks in =
advance.

Best Regards,

Jeffrey Dunn
Info Systems Eng., Lead

Center for Enterprise Modernization
MITRE Corp.

301-429-5377 (Office)
301-731-8862  (FAX)


--_000_3C6F21684E7C954193E6C7C4573B762701D3DD67DAIMCMBX1MITREO_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:D=3D"DAV:" xmln=
s:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois=3D"ht=
tp://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://schema=
s.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3.org/2=
000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http://www=
.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sharepoin=
t/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" xmlns=
:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://schema=
s.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSc=
hema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" xm=
lns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p=3D=
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http://schem=
as.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://schemas.mi=
crosoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.microsof=
t.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformats.org/=
package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlformats=
.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.com/off=
ice/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/package/=
2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpa=
ges" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/typ=
es" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/mess=
ages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibr=
ary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer=
/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:st=3D"=
&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Times New Roman","serif";
	color:black;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:167258771;
	mso-list-type:hybrid;
	mso-list-template-ids:-218337666 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1140920120;
	mso-list-type:hybrid;
	mso-list-template-ids:-403425146 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New Roman">=
<span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:black=
'>Colleagues,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New Roman">=
<span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:black=
'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New Roman">=
<span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:black=
'>We
have been performing some PMTUD tests and have found that different operati=
ng
systems handle PMTUD differently. Specifically, we found that the
&#8220;ping&#8221; application behaves in the following way when the PMTU i=
s
set to 1280 and a 1500 octet ICMPv6 echo request is sent to that routed pat=
h.
The hosts we tested:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New Roman">=
<span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:black=
'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><font
size=3D3 color=3Dblack face=3D"Times New Roman"><span style=3D'font-size:12=
.0pt;
font-family:"Times New Roman","serif";color:black'><span style=3D'mso-list:=
Ignore'>1.<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New Roma=
n"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D3 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;font-family:"Times=
 New Roman","serif";
color:black'>Send one or two un-fragmented echo requests<o:p></o:p></span><=
/font></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><font
size=3D3 color=3Dblack face=3D"Times New Roman"><span style=3D'font-size:12=
.0pt;
font-family:"Times New Roman","serif";color:black'><span style=3D'mso-list:=
Ignore'>2.<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New Roma=
n"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D3 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;font-family:"Times=
 New Roman","serif";
color:black'>Receive the &#8220;Packet Too Big&#8221; ICMPv6 message from t=
he
first interface with the 1280 octet MTU<o:p></o:p></span></font></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><font
size=3D3 color=3Dblack face=3D"Times New Roman"><span style=3D'font-size:12=
.0pt;
font-family:"Times New Roman","serif";color:black'><span style=3D'mso-list:=
Ignore'>3.<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New Roma=
n"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D3 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;font-family:"Times=
 New Roman","serif";
color:black'>Begin to send echo requests in two fragments<o:p></o:p></span>=
</font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New Roman">=
<span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:black=
'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New Roman">=
<span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:black=
'>The
following questions occurred to us:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New Roman">=
<span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:black=
'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D3 color=3Dblack face=3D"Times New Roman"><span style=3D'font-size:12=
.0pt;
font-family:"Times New Roman","serif";color:black'><span style=3D'mso-list:=
Ignore'>1.<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New Roma=
n"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D3 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;font-family:"Times=
 New Roman","serif";
color:black'>Should the hosts re-transmit the ICMPv6 echo request(s) in
fragments?<o:p></o:p></span></font></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><font
size=3D3 color=3Dblack face=3D"Times New Roman"><span style=3D'font-size:12=
.0pt;
font-family:"Times New Roman","serif";color:black'><span style=3D'mso-list:=
Ignore'>2.<font
size=3D1 face=3D"Times New Roman"><span style=3D'font:7.0pt "Times New Roma=
n"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]><font size=3D3 color=3Dblack
face=3D"Times New Roman"><span style=3D'font-size:12.0pt;font-family:"Times=
 New Roman","serif";
color:black'>If not, should the host that sent two echo requests have waite=
d
for a response in support of PMTUD?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New Roman">=
<span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:black=
'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New Roman">=
<span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:black=
'>Any
assistance you can provide, especially commercial specification for shippin=
g
product or other applications, would be most helpful. Many thanks in advanc=
e.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New Roman">=
<span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:black=
'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 color=3Dblack face=3D"Times New Roman">=
<span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif";color:black=
'>Best
Regards, <br>
&nbsp; <br>
Jeffrey Dunn <br>
Info Systems Eng., Lead <br>
&nbsp; <br>
Center for Enterprise Modernization <br>
MITRE Corp. <br>
&nbsp; <br>
301-429-5377 (Office) <br>
301-731-8862&nbsp; (FAX) <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DCalibri><span style=3D'font-size=
:11.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--_000_3C6F21684E7C954193E6C7C4573B762701D3DD67DAIMCMBX1MITREO_--

--===============1783022297==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============1783022297==--

From ipv6-bounces@ietf.org  Wed Jan 21 11:30:07 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6CB743A6A47; Wed, 21 Jan 2009 11:30:07 -0800 (PST)
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 ECC133A6A47 for <ipv6@core3.amsl.com>; Wed, 21 Jan 2009 11:30:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.529
X-Spam-Level: 
X-Spam-Status: No, score=-110.529 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 ChBltQ1tdMnA for <ipv6@core3.amsl.com>; Wed, 21 Jan 2009 11:30:05 -0800 (PST)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 4406F3A6A1F for <ipv6@ietf.org>; Wed, 21 Jan 2009 11:30:05 -0800 (PST)
Received: from tk5-exhub-c103.redmond.corp.microsoft.com (157.54.88.96) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.1.291.1; Wed, 21 Jan 2009 11:31:21 -0800
Received: from TK5-EXMLT-W605V.wingroup.windeploy.ntdev.microsoft.com (157.54.18.79) by tk5-exhub-c103.redmond.corp.microsoft.com (157.54.88.96) with Microsoft SMTP Server id 8.1.291.1; Wed, 21 Jan 2009 11:29:45 -0800
Received: from NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com ([fe80::8de9:51a2:cd62:f122]) by TK5-EXMLT-W605V.wingroup.windeploy.ntdev.microsoft.com ([157.54.18.79]) with mapi; Wed, 21 Jan 2009 11:29:42 -0800
From: Christian Huitema <huitema@windows.microsoft.com>
To: "bob.hinden@nokia.com" <bob.hinden@nokia.com>
Date: Wed, 21 Jan 2009 11:29:40 -0800
Subject: RE: Standard status of RFC 3879
Thread-Topic: Standard status of RFC 3879
Thread-Index: Acl78wTAa92C6IOEQ26SuiIcJnJyFgACynlA
Message-ID: <8EFB68EAE061884A8517F2A755E8B60A19D3AB6792@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
References: <8EFB68EAE061884A8517F2A755E8B60A19D3AB6593@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com> <E5653CB3-3296-4E32-BD83-658EE8343DC5@nokia.com>
In-Reply-To: <E5653CB3-3296-4E32-BD83-658EE8343DC5@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: 6man <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org > From: Bob Hinden [mailto:bob.hinden@nokia.com]
>
> > RFC 3879 was published as proposed standard about 5 years ago. Do we
> > intend to leave it at that stage, or to update its status along the
> > standard track?
> >
>
> What did you have in mind?  Is there a reason to advance it?

I am getting enquiries along the lines of "OK, this was a proposed standard 5 years ago, it has not progressed, does it mean it is now obsolete?"

Of course, I can reply that status doesn't matter, that for all practical purposes Proposed Standards are just as standards as Draft Standards or Internet Standards.

-- Christian Huitema


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Wed Jan 21 11:33:57 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5022D3A6A4A; Wed, 21 Jan 2009 11:33:57 -0800 (PST)
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 DDF9B3A6A47; Wed, 21 Jan 2009 11:33:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 I-JuVFwNkkEM; Wed, 21 Jan 2009 11:33:53 -0800 (PST)
Received: from yop.chewa.net (yop.chewa.net [91.121.105.214]) by core3.amsl.com (Postfix) with ESMTP id A6B943A69ED; Wed, 21 Jan 2009 11:33:53 -0800 (PST)
Received: from basile.remlab.net (unknown [IPv6:2002:591b:3e27:0:211:11ff:fe25:e6b4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: remi) by yop.chewa.net (Postfix) with ESMTP id 437D2492; Wed, 21 Jan 2009 20:33:33 +0100 (CET)
From: =?utf-8?q?R=C3=A9mi_Denis-Courmont?= <rdenis@simphalempin.com>
Organization: Remlab.net
To: ipv6@ietf.org
Subject: Re: End System PMTUD behavior question
Date: Wed, 21 Jan 2009 21:33:27 +0200
User-Agent: KMail/1.9.9
References: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG>
In-Reply-To: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200901212133.30109.rdenis@simphalempin.com>
Cc: "Huang, Frank" <fhuang@mitre.org>, "Sherman, Kurt T." <ksherman@mitre.org>, "Liou, Chern" <csliou@mitre.org>, "steve_eiserman@uscourts.gov" <steve_eiserman@uscourts.gov>, "ipv6-bounces@ietf.org" <ipv6-bounces@ietf.org>, "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, "Grayeli, Parisa" <pgrayeli@mitre.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/pipermail/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>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org TGUgbWVyY3JlZGkgMjEgamFudmllciAyMDA5IDIwOjU2OjIzIER1bm4sIEplZmZyZXkgSC4sIHZv
dXMgYXZleiDDqWNyaXTCoDoKPiBDb2xsZWFndWVzLAo+Cj4gV2UgaGF2ZSBiZWVuIHBlcmZvcm1p
bmcgc29tZSBQTVRVRCB0ZXN0cyBhbmQgaGF2ZSBmb3VuZCB0aGF0IGRpZmZlcmVudAo+IG9wZXJh
dGluZyBzeXN0ZW1zIGhhbmRsZSBQTVRVRCBkaWZmZXJlbnRseS4gU3BlY2lmaWNhbGx5LCB3ZSBm
b3VuZCB0aGF0IHRoZQo+ICJwaW5nIiBhcHBsaWNhdGlvbiBiZWhhdmVzIGluIHRoZSBmb2xsb3dp
bmcgd2F5IHdoZW4gdGhlIFBNVFUgaXMgc2V0IHRvCj4gMTI4MCBhbmQgYSAxNTAwIG9jdGV0IElD
TVB2NiBlY2hvIHJlcXVlc3QgaXMgc2VudCB0byB0aGF0IHJvdXRlZCBwYXRoLiBUaGUKPiBob3N0
cyB3ZSB0ZXN0ZWQ6CgpJJ20gYWZyYWlkIHBpbmcgYXBwbGljYXRpb25zIGFyZSBub3QgcmVwcmVz
ZW50YXRpdmUgb2Ygd2hhdCB0aGUgb3BlcmF0aW5nIApzeXN0ZW0gSVAgc3RhY2tzIGRvLiBCZXNp
ZGVzLCB0aGVyZSBhcmUgbm8gc3RhbmRhcmRzIHJlZ2FyZGluZyB0aGUgYmVoYXZpb3IgCm9mICJw
aW5nIiBpbiBjYXNlIG9mIFBhdGggTVRVIHByb2JsZW1zOyBpdCdzIHJlYWxseSB1cCB0byB0aGUg
aW1wbGVtZW50b3Igb2YgCmVhY2ggInBpbmciIHdoZXRoZXIgdG8gcmVwb3J0IGFuIGVycm9yIG9y
IHRvIHRyYW5zcGFyZW50bHkgZnJhZ21lbnQuCgoKVGhlIGJlaGF2aW9yIG9mIHJlYWwgdHJhbnNw
b3J0IHByb3RvY29scywgc3VjaCBhcyBUQ1AsIERDQ1AgYW5kIFNDVFAgaXMgbW9yZSAKaW50ZXJl
c3Rpbmcgd2hlbiBpdCBjb21lcyB0byBldmFsdWF0aW5nIG9wZXJhdGluZyBzeXN0ZW1zIGFuZCB0
aGVpciBJUCAKc3RhY2tzLgoKLS0gClLDqW1pIERlbmlzLUNvdXJtb250Cmh0dHA6Ly93d3cucmVt
bGFiLm5ldC8KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0KSUVURiBJUHY2IHdvcmtpbmcgZ3JvdXAgbWFpbGluZyBsaXN0
CmlwdjZAaWV0Zi5vcmcKQWRtaW5pc3RyYXRpdmUgUmVxdWVzdHM6IGh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vaXB2NgotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQo=

From ipv6-bounces@ietf.org  Wed Jan 21 11:36:04 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DFA7D3A6A47; Wed, 21 Jan 2009 11:36:03 -0800 (PST)
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 CDA133A6A5C for <ipv6@core3.amsl.com>; Wed, 21 Jan 2009 11:36:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.558
X-Spam-Level: 
X-Spam-Status: No, score=-2.558 tagged_above=-999 required=5 tests=[AWL=0.041,  BAYES_00=-2.599]
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 lFGOmtvJG3uy for <ipv6@core3.amsl.com>; Wed, 21 Jan 2009 11:35:59 -0800 (PST)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id 9E71F3A67F8 for <ipv6@ietf.org>; Wed, 21 Jan 2009 11:35:58 -0800 (PST)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id n0LJZaTg005237; Wed, 21 Jan 2009 21:35:36 +0200
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id n0LJZaNa005233; Wed, 21 Jan 2009 21:35:36 +0200
Date: Wed, 21 Jan 2009 21:35:36 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Christian Huitema <huitema@windows.microsoft.com>
Subject: RE: Standard status of RFC 3879
In-Reply-To: <8EFB68EAE061884A8517F2A755E8B60A19D3AB6792@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
Message-ID: <alpine.LRH.2.00.0901212131170.5113@netcore.fi>
References: <8EFB68EAE061884A8517F2A755E8B60A19D3AB6593@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com> <E5653CB3-3296-4E32-BD83-658EE8343DC5@nokia.com> <8EFB68EAE061884A8517F2A755E8B60A19D3AB6792@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
X-Virus-Scanned: ClamAV 0.94.2/8881/Tue Jan 20 16:48:51 2009 on otso.netcore.fi
X-Virus-Status: Clean
Cc: 6man <ipv6@ietf.org>, "bob.hinden@nokia.com" <bob.hinden@nokia.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org On Wed, 21 Jan 2009, Christian Huitema wrote:
>> What did you have in mind?  Is there a reason to advance it?
>
> I am getting enquiries along the lines of "OK, this was a proposed 
> standard 5 years ago, it has not progressed, does it mean it is now 
> obsolete?"

FWIW, I wouldn't mind advancing it if there is significant new 
evidence or experience to document at the same time.  If not (perhaps 
you were referring to this), just updating on the standards track and 
keeping the document unchanged, doesn't seem to have that much point 
given we need to put energy to other work as well.

Site-locals and ULAs is one area where I suspect our understanding of 
the situation has improved, and will continue to improve.  Timing the 
update properly to gather that understanding is probably a good idea.

-- 
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@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Wed Jan 21 11:44:38 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 008903A68EF; Wed, 21 Jan 2009 11:44:38 -0800 (PST)
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 35A3A3A68EF; Wed, 21 Jan 2009 11:44:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.047
X-Spam-Level: 
X-Spam-Status: No, score=-6.047 tagged_above=-999 required=5 tests=[AWL=0.252,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 c4qfStkB+9Hm; Wed, 21 Jan 2009 11:44:36 -0800 (PST)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 25E433A68CD; Wed, 21 Jan 2009 11:44:36 -0800 (PST)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0LJiJYk024359;  Wed, 21 Jan 2009 14:44:19 -0500
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0LJiJbW024354;  Wed, 21 Jan 2009 14:44:19 -0500
Received: from IMCMBX1.MITRE.ORG ([129.83.29.204]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Wed, 21 Jan 2009 14:44:19 -0500
From: "Dunn, Jeffrey H." <jdunn@mitre.org>
To: =?utf-8?B?UsOpbWkgRGVuaXMtQ291cm1vbnQ=?= <rdenis@simphalempin.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Date: Wed, 21 Jan 2009 14:44:18 -0500
Subject: RE: End System PMTUD behavior question
Thread-Topic: End System PMTUD behavior question
Thread-Index: Acl7/ydWCvtgY5A/T6q3ntngvMF7EQAATi2w
Message-ID: <3C6F21684E7C954193E6C7C4573B762701D3DD687B@IMCMBX1.MITRE.ORG>
References: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG> <200901212133.30109.rdenis@simphalempin.com>
In-Reply-To: <200901212133.30109.rdenis@simphalempin.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "Huang, Frank" <fhuang@mitre.org>, "Sherman, Kurt T." <ksherman@mitre.org>, "Liou, Chern" <csliou@mitre.org>, "steve_eiserman@uscourts.gov" <steve_eiserman@uscourts.gov>, "ipv6-bounces@ietf.org" <ipv6-bounces@ietf.org>, "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, "Grayeli,  Parisa" <pgrayeli@mitre.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/pipermail/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>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org UsOpbWksDQoNCkkgYWdyZWUgd2l0aCB5b3UgYXNzZXJ0aW9ucyBjb25jZXJuaW5nICJwaW5nIiB2
ZXJzdXMgVENQOyBob3dldmVyLCBJIGFtIGxvb2tpbmcgZm9yIHNvbWUgY29uY3JldGUgZG9jdW1l
bnRhdGlvbiBvciBleHBlcmllbmNlcy4NCg0KQmVzdCBSZWdhcmRzLCANCsKgIA0KSmVmZnJleSBE
dW5uIA0KSW5mbyBTeXN0ZW1zIEVuZy4sIExlYWQgDQpNSVRSRSBDb3Jwb3JhdGlvbi4NCigzMDEp
IDQ0OC02OTY1IChtb2JpbGUpDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206
IFLDqW1pIERlbmlzLUNvdXJtb250IFttYWlsdG86cmRlbmlzQHNpbXBoYWxlbXBpbi5jb21dIA0K
U2VudDogV2VkbmVzZGF5LCBKYW51YXJ5IDIxLCAyMDA5IDI6MzMgUE0NClRvOiBpcHY2QGlldGYu
b3JnDQpDYzogRHVubiwgSmVmZnJleSBILjsgaXB2Ni1ib3VuY2VzQGlldGYub3JnOyB2Nm9wc0Bv
cHMuaWV0Zi5vcmc7IFNoZXJtYW4sIEt1cnQgVC47IExpb3UsIENoZXJuOyBzdGV2ZV9laXNlcm1h
bkB1c2NvdXJ0cy5nb3Y7IEh1YW5nLCBGcmFuazsgR3JheWVsaSwgUGFyaXNhDQpTdWJqZWN0OiBS
ZTogRW5kIFN5c3RlbSBQTVRVRCBiZWhhdmlvciBxdWVzdGlvbg0KDQpMZSBtZXJjcmVkaSAyMSBq
YW52aWVyIDIwMDkgMjA6NTY6MjMgRHVubiwgSmVmZnJleSBILiwgdm91cyBhdmV6IMOpY3JpdMKg
Og0KPiBDb2xsZWFndWVzLA0KPg0KPiBXZSBoYXZlIGJlZW4gcGVyZm9ybWluZyBzb21lIFBNVFVE
IHRlc3RzIGFuZCBoYXZlIGZvdW5kIHRoYXQgZGlmZmVyZW50DQo+IG9wZXJhdGluZyBzeXN0ZW1z
IGhhbmRsZSBQTVRVRCBkaWZmZXJlbnRseS4gU3BlY2lmaWNhbGx5LCB3ZSBmb3VuZCB0aGF0IHRo
ZQ0KPiAicGluZyIgYXBwbGljYXRpb24gYmVoYXZlcyBpbiB0aGUgZm9sbG93aW5nIHdheSB3aGVu
IHRoZSBQTVRVIGlzIHNldCB0bw0KPiAxMjgwIGFuZCBhIDE1MDAgb2N0ZXQgSUNNUHY2IGVjaG8g
cmVxdWVzdCBpcyBzZW50IHRvIHRoYXQgcm91dGVkIHBhdGguIFRoZQ0KPiBob3N0cyB3ZSB0ZXN0
ZWQ6DQoNCkknbSBhZnJhaWQgcGluZyBhcHBsaWNhdGlvbnMgYXJlIG5vdCByZXByZXNlbnRhdGl2
ZSBvZiB3aGF0IHRoZSBvcGVyYXRpbmcgDQpzeXN0ZW0gSVAgc3RhY2tzIGRvLiBCZXNpZGVzLCB0
aGVyZSBhcmUgbm8gc3RhbmRhcmRzIHJlZ2FyZGluZyB0aGUgYmVoYXZpb3IgDQpvZiAicGluZyIg
aW4gY2FzZSBvZiBQYXRoIE1UVSBwcm9ibGVtczsgaXQncyByZWFsbHkgdXAgdG8gdGhlIGltcGxl
bWVudG9yIG9mIA0KZWFjaCAicGluZyIgd2hldGhlciB0byByZXBvcnQgYW4gZXJyb3Igb3IgdG8g
dHJhbnNwYXJlbnRseSBmcmFnbWVudC4NCg0KDQpUaGUgYmVoYXZpb3Igb2YgcmVhbCB0cmFuc3Bv
cnQgcHJvdG9jb2xzLCBzdWNoIGFzIFRDUCwgRENDUCBhbmQgU0NUUCBpcyBtb3JlIA0KaW50ZXJl
c3Rpbmcgd2hlbiBpdCBjb21lcyB0byBldmFsdWF0aW5nIG9wZXJhdGluZyBzeXN0ZW1zIGFuZCB0
aGVpciBJUCANCnN0YWNrcy4NCg0KLS0gDQpSw6ltaSBEZW5pcy1Db3VybW9udA0KaHR0cDovL3d3
dy5yZW1sYWIubmV0Lw0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KSUVURiBJUHY2IHdvcmtpbmcgZ3JvdXAgbWFpbGlu
ZyBsaXN0CmlwdjZAaWV0Zi5vcmcKQWRtaW5pc3RyYXRpdmUgUmVxdWVzdHM6IGh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaXB2NgotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQo=

From ipv6-bounces@ietf.org  Wed Jan 21 12:00:53 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FD6928C221; Wed, 21 Jan 2009 12:00:53 -0800 (PST)
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 2191C28C226; Wed, 21 Jan 2009 12:00:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 jBmVE4JvWZiI; Wed, 21 Jan 2009 12:00:51 -0800 (PST)
Received: from postal.iol.unh.edu (postal.iol.unh.edu [132.177.123.84]) by core3.amsl.com (Postfix) with ESMTP id D72C128C216; Wed, 21 Jan 2009 12:00:42 -0800 (PST)
Received: from chinacat.iol.unh.edu (chinacat.iol.unh.edu [132.177.125.46]) by postal.iol.unh.edu (8.14.0/8.14.0) with ESMTP id n0LK0J7k019245 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 21 Jan 2009 15:00:19 -0500
Message-Id: <42A4D5E1-C552-434C-90E3-DA3EF4A78688@iol.unh.edu>
From: Thomas Peterson <thomasp@iol.unh.edu>
To: "Dunn, Jeffrey H." <jdunn@mitre.org>
In-Reply-To: <3C6F21684E7C954193E6C7C4573B762701D3DD687B@IMCMBX1.MITRE.ORG>
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: End System PMTUD behavior question
Date: Wed, 21 Jan 2009 15:00:20 -0500
References: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG> <200901212133.30109.rdenis@simphalempin.com> <3C6F21684E7C954193E6C7C4573B762701D3DD687B@IMCMBX1.MITRE.ORG>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV 0.94/8885/Wed Jan 21 12:48:08 2009 on postal.iol.unh.edu
X-Virus-Status: Clean
Cc: "ipv6-bounces@ietf.org" <ipv6-bounces@ietf.org>, "Liou, Chern" <csliou@mitre.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "Sherman, Kurt T." <ksherman@mitre.org>, "steve_eiserman@uscourts.gov" <steve_eiserman@uscourts.gov>, "Huang, Frank" <fhuang@mitre.org>, "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, "Grayeli, Parisa" <pgrayeli@mitre.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/pipermail/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>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org Hi Jeffrey,

This is Thomas Peterson from the InterOperability Laboratory at UNH.

We have done extensive testing in this area and would be happy to work  =

with you off line to examine this scenario.

If you would like we can even set up your test topology in our lab.

Thanks,
Tom

On Jan 21, 2009, at 2:44 PM, Dunn, Jeffrey H. wrote:

> R=E9mi,
>
> I agree with you assertions concerning "ping" versus TCP; however, I  =

> am looking for some concrete documentation or experiences.
>
> Best Regards,
>
> Jeffrey Dunn
> Info Systems Eng., Lead
> MITRE Corporation.
> (301) 448-6965 (mobile)
>
>
> -----Original Message-----
> From: R=E9mi Denis-Courmont [mailto:rdenis@simphalempin.com]
> Sent: Wednesday, January 21, 2009 2:33 PM
> To: ipv6@ietf.org
> Cc: Dunn, Jeffrey H.; ipv6-bounces@ietf.org; v6ops@ops.ietf.org;  =

> Sherman, Kurt T.; Liou, Chern; steve_eiserman@uscourts.gov; Huang,  =

> Frank; Grayeli, Parisa
> Subject: Re: End System PMTUD behavior question
>
> Le mercredi 21 janvier 2009 20:56:23 Dunn, Jeffrey H., vous avez  =

> =E9crit :
>> Colleagues,
>>
>> We have been performing some PMTUD tests and have found that  =

>> different
>> operating systems handle PMTUD differently. Specifically, we found  =

>> that the
>> "ping" application behaves in the following way when the PMTU is  =

>> set to
>> 1280 and a 1500 octet ICMPv6 echo request is sent to that routed  =

>> path. The
>> hosts we tested:
>
> I'm afraid ping applications are not representative of what the  =

> operating
> system IP stacks do. Besides, there are no standards regarding the  =

> behavior
> of "ping" in case of Path MTU problems; it's really up to the  =

> implementor of
> each "ping" whether to report an error or to transparently fragment.
>
>
> The behavior of real transport protocols, such as TCP, DCCP and SCTP  =

> is more
> interesting when it comes to evaluating operating systems and their IP
> stacks.
>
> -- =

> R=E9mi Denis-Courmont
> http://www.remlab.net/
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Wed Jan 21 12:27:11 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B48EA28C105; Wed, 21 Jan 2009 12:27:11 -0800 (PST)
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 BAB4B3A6A7C for <ipv6@core3.amsl.com>; Wed, 21 Jan 2009 12:27:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.046
X-Spam-Level: 
X-Spam-Status: No, score=-6.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
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 iU0TVwNxZGfI for <ipv6@core3.amsl.com>; Wed, 21 Jan 2009 12:27:10 -0800 (PST)
Received: from mailgate-internal3.sri.com (mailgate-internal3.SRI.COM [128.18.84.113]) by core3.amsl.com (Postfix) with SMTP id E63783A6937 for <ipv6@ietf.org>; Wed, 21 Jan 2009 12:27:09 -0800 (PST)
Received: from smssmtp-internal1.sri.com (128.18.84.115) by mailgate-internal3.sri.com with SMTP; 21 Jan 2009 20:26:52 -0000
X-AuditID: 80125473-a7b88bb000000aa9-c7-4977850c686b
Received: from srimail1.sri.com (srimail1.SRI.COM [128.18.30.11]) by smssmtp-internal1.sri.com (Symantec Mail Security) with ESMTP id 6C66C21AF2D for <ipv6@ietf.org>; Wed, 21 Jan 2009 12:26:52 -0800 (PST)
Received: from [192.168.1.2] (nj-76-1-246-80.dhcp.embarqhsd.net [76.1.246.80]) by mail.sri.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0KDU00MQC8SR4X00@mail.sri.com> for ipv6@ietf.org; Wed, 21 Jan 2009 12:26:52 -0800 (PST)
Date: Wed, 21 Jan 2009 15:26:50 -0500
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
Subject: Re: Standard status of RFC 3879
In-reply-to: <E5653CB3-3296-4E32-BD83-658EE8343DC5@nokia.com>
To: bob.hinden@nokia.com
Message-id: <4977850A.80207@sri.com>
MIME-version: 1.0
References: <8EFB68EAE061884A8517F2A755E8B60A19D3AB6593@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com> <E5653CB3-3296-4E32-BD83-658EE8343DC5@nokia.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
X-Brightmail-Tracker: AAAAAA==
Cc: Christian Huitema <huitema@windows.microsoft.com>, 6man <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org RFC 4291 cites it (includes it by reference) but not as a normative 
reference, but also restates the action taken by RFC 3879.  Assuming RFC 
4291 progresses along the standards track making the deprecation of 
Site-local a "standard" is there any need to also promote 3879?   Also, 
since 4291 obsoletes 3351, the definition of site-local address is 
effectively erased, as if it never existed, although the text does not 
say MUST NOT, and allows for the use of site-local by preexisting 
implementations.

In the latest version of the US DoD IPv6 profiles, RFC 3879 is mentioned 
only as a footnote because RFC 4291 appears to be definitive enough.

Bob Hinden wrote:
> Christian,
>
>> RFC 3879 was published as proposed standard about 5 years ago. Do we 
>> intend to leave it at that stage, or to update its status along the 
>> standard track?
>>
>
> What did you have in mind?  Is there a reason to advance it?
>
> Bob
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research 
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Wed Jan 21 12:31:22 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B3D03A69E9; Wed, 21 Jan 2009 12:31:22 -0800 (PST)
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 35C333A69E9 for <ipv6@core3.amsl.com>; Wed, 21 Jan 2009 12:31:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.512
X-Spam-Level: 
X-Spam-Status: No, score=-2.512 tagged_above=-999 required=5 tests=[AWL=0.087,  BAYES_00=-2.599]
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 yQGHWVA5dzy9 for <ipv6@core3.amsl.com>; Wed, 21 Jan 2009 12:31:20 -0800 (PST)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by core3.amsl.com (Postfix) with ESMTP id 663B93A6937 for <ipv6@ietf.org>; Wed, 21 Jan 2009 12:31:20 -0800 (PST)
Received: by rv-out-0506.google.com with SMTP id b25so3895306rvf.49 for <ipv6@ietf.org>; Wed, 21 Jan 2009 12:31:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=lC3yN0QHMl8fYJpC3VDm+9sfz9doq8HN/fb0jEtGBzQ=; b=JcH4r9GgQyhGk7LJ2Qb7SpSN3LlHj1l00v7yBHE+1fSU85ueljNcdpMPAmxsMXVOw+ 6FSNXfXbqkdo4q6q4nc1zoK/jBNfib1CmB7OZHLMwQHji8e4lMVV7RjL1hT4IdO1ZufM gwV21jQjZpbybPh3I2xXuXxxh9FHGLo3gt+oE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=FrWnPxmlwCFuoWNIzSaEStd7uqu4FfMM8Bo4P2a3qlXpfGm5/258QPz5CwQ1ivB+Jz 2PMKWQMHU0UQOwELWqw4VEOdiR/lJTOGhbJ3mIT0kY6OQTX9h6pU2Aasyr4316GdYu0D NhEhlqhb8mfzGj4DOukyiC04HVWwDmiO+TtaI=
Received: by 10.141.45.16 with SMTP id x16mr2735245rvj.7.1232569863953; Wed, 21 Jan 2009 12:31:03 -0800 (PST)
Received: from ?130.216.38.124? (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id f21sm16327032rvb.7.2009.01.21.12.31.02 (version=SSLv3 cipher=RC4-MD5); Wed, 21 Jan 2009 12:31:03 -0800 (PST)
Message-ID: <49778604.4010703@gmail.com>
Date: Thu, 22 Jan 2009 09:31:00 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
Subject: Re: Standard status of RFC 3879
References: <8EFB68EAE061884A8517F2A755E8B60A19D3AB6593@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com> <E5653CB3-3296-4E32-BD83-658EE8343DC5@nokia.com> <8EFB68EAE061884A8517F2A755E8B60A19D3AB6792@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com> <alpine.LRH.2.00.0901212131170.5113@netcore.fi>
In-Reply-To: <alpine.LRH.2.00.0901212131170.5113@netcore.fi>
Cc: Christian Huitema <huitema@windows.microsoft.com>, 6man <ipv6@ietf.org>, "bob.hinden@nokia.com" <bob.hinden@nokia.com>
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org Pekka,

On 2009-01-22 08:35, Pekka Savola wrote:
> On Wed, 21 Jan 2009, Christian Huitema wrote:
>>> What did you have in mind?  Is there a reason to advance it?
>>
>> I am getting enquiries along the lines of "OK, this was a proposed
>> standard 5 years ago, it has not progressed, does it mean it is now
>> obsolete?"
> 
> FWIW, I wouldn't mind advancing it if there is significant new evidence
> or experience to document at the same time.  If not (perhaps you were
> referring to this), just updating on the standards track and keeping the
> document unchanged, doesn't seem to have that much point given we need
> to put energy to other work as well.

Well, I think Christian's point is valid. There are still text books that
list site-local as valid, and in my XP box I find:

       DNS Servers . . . . . . . . . . . : 130.216.xx.xxx
                                           130.216.xx.xxx
                                           fec0:0:0:ffff::1%2
                                           fec0:0:0:ffff::2%2
                                           fec0:0:0:ffff::3%2

I think that simply reclassifying 3879 as DS would be a Good Thing
and requires minimal effort.

> 
> Site-locals and ULAs is one area where I suspect our understanding of
> the situation has improved, and will continue to improve.  Timing the
> update properly to gather that understanding is probably a good idea.

I don't believe there is enough deployment experience with ULAs yet.
I wouldn't personally want to couple the 3879 issue with re-opening
the ULA discussion.

     Brian
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Wed Jan 21 12:36:25 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 643A43A6A70; Wed, 21 Jan 2009 12:36:25 -0800 (PST)
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 BA7393A69ED; Wed, 21 Jan 2009 12:36:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.897
X-Spam-Level: 
X-Spam-Status: No, score=-5.897 tagged_above=-999 required=5 tests=[AWL=0.702,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 PCyDela959Db; Wed, 21 Jan 2009 12:36:23 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 010323A6937; Wed, 21 Jan 2009 12:36:22 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,302,1231113600"; d="scan'208";a="131838859"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-1.cisco.com with ESMTP; 21 Jan 2009 20:36:06 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n0LKa6cY001366;  Wed, 21 Jan 2009 12:36:06 -0800
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n0LKa5if013425; Wed, 21 Jan 2009 20:36:06 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 21 Jan 2009 15:36:05 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: End System PMTUD behavior question
Date: Wed, 21 Jan 2009 15:35:16 -0500
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0632C176@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: End System PMTUD behavior question
Thread-Index: Acl7+fSDtCRQmHdATNy7UebOW+92QAACmYbg
References: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Dunn, Jeffrey H." <jdunn@mitre.org>, <ipv6-bounces@ietf.org>, <v6ops@ops.ietf.org>, "6man mailing list" <ipv6@ietf.org>
X-OriginalArrivalTime: 21 Jan 2009 20:36:05.0501 (UTC) FILETIME=[E1FF9AD0:01C97C07]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1348; t=1232570166; x=1233434166; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=shemant@cisco.com; z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco. com> |Subject:=20RE=3A=20End=20System=20PMTUD=20behavior=20quest ion |Sender:=20; bh=5VcY43xFzxCP+Hg7gwu5fG4zFKyh0ND6GiJqnqyBUCQ=; b=ufrza3ekF5veDe40jDmKro5mNoqsul7uTdtRW1mnudt9p3uDb8T1CTQbcs T9inGJTB9tpgGb9wVlX4+9ISk+Hmn2HZScEUBWPvuc1qQ11fP1H5/bUcdt+m NyecpZ9oN6;
Authentication-Results: sj-dkim-3; header.From=shemant@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); 
Cc: "Huang, Frank" <fhuang@mitre.org>, "Sherman, Kurt T." <ksherman@mitre.org>, "Grayeli, Parisa" <pgrayeli@mitre.org>, "Liou, Chern" <csliou@mitre.org>, steve_eiserman@uscourts.gov
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org > The following questions occurred to us:

>  1. Should the hosts re-transmit the ICMPv6 echo request(s) in
fragments? 

If the ICMPv6 echo reqs were being used for PMTUD, the answer should be
a No.  The host just received an Indication of Too Big that also said
the PMTU is 1280, so the host should be sending any subsequent packets
keeping PMTU of 1280 in mind without have to fragment. Then my question
is, if ICMPv6 is not being used for PMTUD, then for what purpose is
ICMPv6 being used such that an ICMPv6 req of 1500 is needed when a req
of size 1280 can be sent?

>  2. If not, should the host that sent two echo requests have waited
for a response in support of PMTUD? 

PMTUD does recommend a host send a probe and wait for a timeout interval
before sending another probe. The RFCs recommend five times larger
timeout value that the normal timeout of the protocol/app being used to
probe.  So, say, the ICMPv6 timeout being used in your test is 2 secs,
then the host should wait for 10 secs for a reply.  See RFC 4821 for
timeout recommendations for how long to wait for a probe reply.  In your
test case, I have got to believe, the Too Big error reached the host in
10 secs of sending the ICMPv6 req - the first hop router is most likely
to catch the Too Big condition and respond to the probe.

Hemant 

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Wed Jan 21 14:24:42 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E18D28C13A; Wed, 21 Jan 2009 14:24:42 -0800 (PST)
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 1D27728C10A; Wed, 21 Jan 2009 14:24:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.114
X-Spam-Level: 
X-Spam-Status: No, score=-6.114 tagged_above=-999 required=5 tests=[AWL=0.485,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 wOrjcGWaQTZ9; Wed, 21 Jan 2009 14:24:39 -0800 (PST)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id A1D8D28C13A; Wed, 21 Jan 2009 14:24:39 -0800 (PST)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0LMOMuG001087;  Wed, 21 Jan 2009 17:24:22 -0500
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0LMOK0W000934;  Wed, 21 Jan 2009 17:24:20 -0500
Received: from IMCMBX1.MITRE.ORG ([129.83.29.204]) by imchub2.MITRE.ORG ([129.83.29.74]) with mapi; Wed, 21 Jan 2009 17:24:20 -0500
From: "Dunn, Jeffrey H." <jdunn@mitre.org>
To: Thomas Peterson <thomasp@iol.unh.edu>
Date: Wed, 21 Jan 2009 17:24:18 -0500
Subject: RE: End System PMTUD behavior question
Thread-Topic: End System PMTUD behavior question
Thread-Index: Acl8AumHvABBPVEsRNuqz40l5WxhqwAE/RWA
Message-ID: <3C6F21684E7C954193E6C7C4573B762701D3DD69D1@IMCMBX1.MITRE.ORG>
References: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG> <200901212133.30109.rdenis@simphalempin.com> <3C6F21684E7C954193E6C7C4573B762701D3DD687B@IMCMBX1.MITRE.ORG> <42A4D5E1-C552-434C-90E3-DA3EF4A78688@iol.unh.edu>
In-Reply-To: <42A4D5E1-C552-434C-90E3-DA3EF4A78688@iol.unh.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "ipv6-bounces@ietf.org" <ipv6-bounces@ietf.org>, "Liou, Chern" <csliou@mitre.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "Sherman, Kurt T." <ksherman@mitre.org>, "steve_eiserman@uscourts.gov" <steve_eiserman@uscourts.gov>, "Huang, Frank" <fhuang@mitre.org>, "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, "Grayeli, Parisa" <pgrayeli@mitre.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/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org Thomas,

We would be happy to see any results you may have concerning application be=
havior during PMTUD. =


Best Regards, =

=A0 =

Jeffrey Dunn =

Info Systems Eng., Lead =

MITRE Corporation.
(301) 448-6965 (mobile)

-----Original Message-----
From: Thomas Peterson [mailto:thomasp@iol.unh.edu] =

Sent: Wednesday, January 21, 2009 3:00 PM
To: Dunn, Jeffrey H.
Cc: R=E9mi Denis-Courmont; ipv6@ietf.org; Huang, Frank; Sherman, Kurt T.; L=
iou, Chern; steve_eiserman@uscourts.gov; ipv6-bounces@ietf.org; v6ops@ops.i=
etf.org; Grayeli, Parisa
Subject: Re: End System PMTUD behavior question

Hi Jeffrey,

This is Thomas Peterson from the InterOperability Laboratory at UNH.

We have done extensive testing in this area and would be happy to work  =

with you off line to examine this scenario.

If you would like we can even set up your test topology in our lab.

Thanks,
Tom

On Jan 21, 2009, at 2:44 PM, Dunn, Jeffrey H. wrote:

> R=E9mi,
>
> I agree with you assertions concerning "ping" versus TCP; however, I  =

> am looking for some concrete documentation or experiences.
>
> Best Regards,
>
> Jeffrey Dunn
> Info Systems Eng., Lead
> MITRE Corporation.
> (301) 448-6965 (mobile)
>
>
> -----Original Message-----
> From: R=E9mi Denis-Courmont [mailto:rdenis@simphalempin.com]
> Sent: Wednesday, January 21, 2009 2:33 PM
> To: ipv6@ietf.org
> Cc: Dunn, Jeffrey H.; ipv6-bounces@ietf.org; v6ops@ops.ietf.org;  =

> Sherman, Kurt T.; Liou, Chern; steve_eiserman@uscourts.gov; Huang,  =

> Frank; Grayeli, Parisa
> Subject: Re: End System PMTUD behavior question
>
> Le mercredi 21 janvier 2009 20:56:23 Dunn, Jeffrey H., vous avez  =

> =E9crit :
>> Colleagues,
>>
>> We have been performing some PMTUD tests and have found that  =

>> different
>> operating systems handle PMTUD differently. Specifically, we found  =

>> that the
>> "ping" application behaves in the following way when the PMTU is  =

>> set to
>> 1280 and a 1500 octet ICMPv6 echo request is sent to that routed  =

>> path. The
>> hosts we tested:
>
> I'm afraid ping applications are not representative of what the  =

> operating
> system IP stacks do. Besides, there are no standards regarding the  =

> behavior
> of "ping" in case of Path MTU problems; it's really up to the  =

> implementor of
> each "ping" whether to report an error or to transparently fragment.
>
>
> The behavior of real transport protocols, such as TCP, DCCP and SCTP  =

> is more
> interesting when it comes to evaluating operating systems and their IP
> stacks.
>
> -- =

> R=E9mi Denis-Courmont
> http://www.remlab.net/
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Wed Jan 21 14:36:07 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E25613A6937; Wed, 21 Jan 2009 14:36:06 -0800 (PST)
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 5252D3A6937; Wed, 21 Jan 2009 14:36:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.102
X-Spam-Level: 
X-Spam-Status: No, score=-6.102 tagged_above=-999 required=5 tests=[AWL=0.497,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 3xrtEdvRTP4V; Wed, 21 Jan 2009 14:36:04 -0800 (PST)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 6384D3A692D; Wed, 21 Jan 2009 14:36:04 -0800 (PST)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0LMZlc3016137;  Wed, 21 Jan 2009 17:35:47 -0500
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0LMZlkI016132;  Wed, 21 Jan 2009 17:35:47 -0500
Received: from IMCMBX1.MITRE.ORG ([129.83.29.204]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Wed, 21 Jan 2009 17:35:47 -0500
From: "Dunn, Jeffrey H." <jdunn@mitre.org>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Date: Wed, 21 Jan 2009 17:35:46 -0500
Subject: RE: End System PMTUD behavior question
Thread-Topic: End System PMTUD behavior question
Thread-Index: Acl7+fSDtCRQmHdATNy7UebOW+92QAACmYbgAASrC5A=
Message-ID: <3C6F21684E7C954193E6C7C4573B762701D3DD69E6@IMCMBX1.MITRE.ORG>
References: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG> <B00EDD615E3C5344B0FFCBA910CF7E1D0632C176@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0632C176@xmb-rtp-20e.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "ipv6-bounces@ietf.org" <ipv6-bounces@ietf.org>, "Sherman, Kurt T." <ksherman@mitre.org>, 6man mailing list <ipv6@ietf.org>, "Liou, Chern" <csliou@mitre.org>, "steve_eiserman@uscourts.gov" <steve_eiserman@uscourts.gov>, "Huang, Frank" <fhuang@mitre.org>, "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, "Grayeli, Parisa" <pgrayeli@mitre.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/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org Hemant,

I do not understand your answer to question 1.  How would the purpose of a =
user sending ICMPv6 echo requests bear on system behavior? Also, unless the=
 operating system has a facility to pass the PMTU size to the application, =
e.g., the MMS_S value mentioned in RFC 1981, AND the application can make u=
se of the information. There is no expectation that the application, e.g., =
DNS, or the layer above IPv6, e.g., UDP, can make use of the information in=
 RFC 1981; therefore your assertion that the host should be sending packets=
 within the PMTU is unreasonable.

Many thanks for pointing out RFC 4821 in answer to question 2. I had forgot=
ten about that and, interestingly, it does not appear in the NIST IPv6 prof=
ile, which we are using to guide our testing. =


Best Regards, =

=A0 =

Jeffrey Dunn =

Info Systems Eng., Lead =

MITRE Corporation.
(301) 448-6965 (mobile)


-----Original Message-----
From: Hemant Singh (shemant) [mailto:shemant@cisco.com] =

Sent: Wednesday, January 21, 2009 3:35 PM
To: Dunn, Jeffrey H.; ipv6-bounces@ietf.org; v6ops@ops.ietf.org; 6man maili=
ng list
Cc: Sherman, Kurt T.; Liou, Chern; steve_eiserman@uscourts.gov; Huang, Fran=
k; Grayeli, Parisa
Subject: RE: End System PMTUD behavior question

> The following questions occurred to us:

>  1. Should the hosts re-transmit the ICMPv6 echo request(s) in
fragments? =


If the ICMPv6 echo reqs were being used for PMTUD, the answer should be
a No.  The host just received an Indication of Too Big that also said
the PMTU is 1280, so the host should be sending any subsequent packets
keeping PMTU of 1280 in mind without have to fragment. Then my question
is, if ICMPv6 is not being used for PMTUD, then for what purpose is
ICMPv6 being used such that an ICMPv6 req of 1500 is needed when a req
of size 1280 can be sent?

>  2. If not, should the host that sent two echo requests have waited
for a response in support of PMTUD? =


PMTUD does recommend a host send a probe and wait for a timeout interval
before sending another probe. The RFCs recommend five times larger
timeout value that the normal timeout of the protocol/app being used to
probe.  So, say, the ICMPv6 timeout being used in your test is 2 secs,
then the host should wait for 10 secs for a reply.  See RFC 4821 for
timeout recommendations for how long to wait for a probe reply.  In your
test case, I have got to believe, the Too Big error reached the host in
10 secs of sending the ICMPv6 req - the first hop router is most likely
to catch the Too Big condition and respond to the probe.

Hemant =


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Thu Jan 22 03:10:36 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66B1D3A69EB; Thu, 22 Jan 2009 03:10:36 -0800 (PST)
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 80ACE3A692E for <ipv6@core3.amsl.com>; Thu, 22 Jan 2009 03:10:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599]
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 VBlWSp78Nr0z for <ipv6@core3.amsl.com>; Thu, 22 Jan 2009 03:10:34 -0800 (PST)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id 371D83A69EB for <ipv6@ietf.org>; Thu, 22 Jan 2009 03:10:34 -0800 (PST)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id n0MBAC1V029734; Thu, 22 Jan 2009 13:10:12 +0200
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id n0MBAA1O029730; Thu, 22 Jan 2009 13:10:11 +0200
Date: Thu, 22 Jan 2009 13:10:10 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Standard status of RFC 3879
In-Reply-To: <49778604.4010703@gmail.com>
Message-ID: <alpine.LRH.2.00.0901221308080.29459@netcore.fi>
References: <8EFB68EAE061884A8517F2A755E8B60A19D3AB6593@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com> <E5653CB3-3296-4E32-BD83-658EE8343DC5@nokia.com> <8EFB68EAE061884A8517F2A755E8B60A19D3AB6792@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com> <alpine.LRH.2.00.0901212131170.5113@netcore.fi> <49778604.4010703@gmail.com>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on otso.netcore.fi
X-Virus-Status: Clean
Cc: Christian Huitema <huitema@windows.microsoft.com>, "bob.hinden@nokia.com" <bob.hinden@nokia.com>, 6man <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/pipermail/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org On Thu, 22 Jan 2009, Brian E Carpenter wrote:
> Well, I think Christian's point is valid. There are still text books that
> list site-local as valid, and in my XP box I find:
>
>       DNS Servers . . . . . . . . . . . : 130.216.xx.xxx
>                                           130.216.xx.xxx
>                                           fec0:0:0:ffff::1%2
>                                           fec0:0:0:ffff::2%2
>                                           fec0:0:0:ffff::3%2
>
> I think that simply reclassifying 3879 as DS would be a Good Thing
> and requires minimal effort.

FWIW, I see this more as evidence that site-local deprecation hasn't 
been as successful as we could hope.  Putting 3879 to AS doesn't fix 
above.

-- 
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@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Thu Jan 22 12:38:31 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0D533A6A07; Thu, 22 Jan 2009 12:38:31 -0800 (PST)
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 43FB228C28B; Thu, 22 Jan 2009 12:38:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 VqUyKbUB0AQ2; Thu, 22 Jan 2009 12:38:23 -0800 (PST)
Received: from postal.iol.unh.edu (postal.iol.unh.edu [132.177.123.84]) by core3.amsl.com (Postfix) with ESMTP id 807F63A69B4; Thu, 22 Jan 2009 12:38:22 -0800 (PST)
Received: from chinacat.iol.unh.edu (chinacat.iol.unh.edu [132.177.125.46]) by postal.iol.unh.edu (8.14.0/8.14.0) with ESMTP id n0MKc2ai026748 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 22 Jan 2009 15:38:03 -0500
Message-Id: <18F8D12C-DAA0-4F30-B405-9F54C15EACB4@iol.unh.edu>
From: Thomas Peterson <thomasp@iol.unh.edu>
To: "Dunn, Jeffrey H." <jdunn@mitre.org>
In-Reply-To: <3C6F21684E7C954193E6C7C4573B762701D3DD69D1@IMCMBX1.MITRE.ORG>
Content-Type: multipart/mixed; boundary=Apple-Mail-27-946412721
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: End System PMTUD behavior question
Date: Thu, 22 Jan 2009 15:38:03 -0500
References: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG> <200901212133.30109.rdenis@simphalempin.com> <3C6F21684E7C954193E6C7C4573B762701D3DD687B@IMCMBX1.MITRE.ORG> <42A4D5E1-C552-434C-90E3-DA3EF4A78688@iol.unh.edu> <3C6F21684E7C954193E6C7C4573B762701D3DD69D1@IMCMBX1.MITRE.ORG>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV 0.94/8892/Thu Jan 22 09:34:53 2009 on postal.iol.unh.edu
X-Virus-Status: Clean
Cc: "ipv6-bounces@ietf.org" <ipv6-bounces@ietf.org>, "Liou, Chern" <csliou@mitre.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "Sherman, Kurt T." <ksherman@mitre.org>, "steve_eiserman@uscourts.gov" <steve_eiserman@uscourts.gov>, "Huang, Frank" <fhuang@mitre.org>, "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, "Grayeli, Parisa" <pgrayeli@mitre.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/pipermail/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>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org --Apple-Mail-27-946412721
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Hi Jeffrey,

I have attached a picture which shows one of the topologies we use for  
our PMTUD tests.

In this test case we transmit an Echo Request from REF-Host2 to TAR- 
Host1 with a packet size of 1500 bytes. REF-Host2 fragments the Echo  
Request it transmits. TAR-Host1 replies to this Echo Request with an  
Echo Reply to REF-Host2 with a size of 1500 bytes that is not  
fragmented. TAR-Router1 sends a Packet Too Big message in response as  
this Echo Reply is too large to forward onto Network 2.

In all of the cases we have seen TAR-Host1 does fragment future Echo  
Replies to REF-Host2, however, it does not retransmit any Echo Replies  
for Echo Requests received prior to receiving the Packet Too Big  
message from TAR-Router1.

Additionally from the tests we have performed in our lab if TAR-Host1  
were to send an Echo Request with a packet size of 1500 bytes TAR- 
Router1 would send a Packet Too Big message in response. In all cases  
we have seen TAR-Host1 would not re-transmit this Echo Request and  
this would be counted as packet loss in the ping command results.

If this does not ideally match your test scenario we'd be happy to  
work together off-line to replicate your scenario.

Thanks,
Tom


--Apple-Mail-27-946412721
Content-Disposition: inline;
	filename=MTU_Interoperability_Topology.png
Content-Type: image/png;
	x-mac-hide-extension=yes;
	x-unix-mode=0644;
	name="MTU_Interoperability_Topology.png"
Content-Transfer-Encoding: base64

iVBORw0KGgoAAAANSUhEUgAAAPQAAAELCAIAAABh/jzRAAAOT2lDQ1BJQ0MgUHJvZmlsZQAAeAGt
l3c4lW/8x++z7ZktK0nIjuy997H3OMceHY6VUYiIIrNBRhSSnZ1RQjaZlRCSlUhJhN9RX31//3yv
3z+/+7qe636d+3nfn/t+ns9zX+/zAYDylSMO5wUFAHj7+PuhNZQ5LCytOFBvAAQgAAkgB+SOGDxO
ydBQlyD5j7Y9TlAT2si5o1j/IfqvYQo/woIAQAQIghOuf1jxiJ3+sMkRB/nj/AkatyPGuDliCRxG
YAE/E7QKgYsITOH6h+uP2OkPvzriQIzr0dxJAJA0Plh3HwBQawSWxzrjMYTbR+vaY/EYbwLfIPCG
t/dFQnzKo/i8GJwfYS5lAYG5j94LoSc0vAgAcp4AQNn+HbNRAODJYwBoS/8dO+MCAD0CgGarf8e2
0L/fFYR+EO8iJvo7HIRMGQDE9OHhFg9hbykA7CcfHu49ODzczwcANgVAmxcmwC/wt5bwIJB+AP6v
33+e+Z8ZMEJyjhLMDKxBM0QC0gZ1h4nBeRGqyJuoXeJUUjlyKMUQVSVNwgkXehlGCqZZluqT19nt
OeVPcXDv8ozylvJFCqAFmYQmRG6JSYuPSfhK7kiFSH+VtZerkF9T5FYyUo5UeaI6ovZdg1pTSEtd
20wHq+ut56cfaBBiGGIUjPY1xpl4mPqbXTaPsbhhmWKVZp1mk2p7yy7BPsbhsmOgky/GDevgbOti
5mropuuu5nHWE+U57/XcO8/n6kUXnI6viB8Lnhi/478cMB04ETQU3H+pP2QgdDBsMLzv8ssrjRHV
keVRFVcro2tjmq91xg7EjV1/Gz+XsHRj5eZa4mrS4q3Z5MmUsdSPad8zkLfp73Dd5b8nkimRJXlf
Ils051wuTx7rA8p8WP52weLD8UevChuLWoufP35Z0vmkvbStrKG8vOJBZXpVdLX/U8cavdoLdafq
Kep/Niw2vm5qfpbejG0RaTlo7Wm7+9z5hWg7pH34ZV6HX6d6F3PXl1ft3Vk9/r36fXz9iP6JgcxB
uyGuoaXhyteXRpRHyUYnxh6Me02cn/g1+eLNtbea70jedU9Fv1d4vzf9fObarM4Hyg8jc6nzhgvk
C90fIxcvLH7+lL1ksHS4XLZis0qyWrvm9Jn288R6/hffDYVN8s2Zr5Vb0d8sv4tuU2x//jG4U/ez
YDd1L/ZXxH7YQcgh+vCQkH86oAnSwS4EB9mFlsFi4bGIWhQF0W0SWdId8kHKPOpgWlU6Gvo+xhvM
eqxMJ1fYmziTTvmc1j4jeJaEb0GgRjBaWFVkRyz/vKxE7wVdqRYZHlkfufvyPQrflE4qq6hgVePU
itV7NVa0kNqcOjK6+npY/UsGNw3zjJ6iXxp3m3SYtpo1mddZVFtWWVVZV9pU2T61q7dvdehyHHSa
wMxjN5x/uRK7Mbqze1B6/PCc9urwfuKTfDEYZ+kr58eJh+E/+fcGlAemBV0Ktr+kFSIayhwGCfsU
3nu5/MrtiIjIgCiXq3bRljFm10xjjeOMrqPjjRMMb+jf1EpUTJK4xZ/MmyKWqphmkG6d4Xzb847P
Xdw970y3LMf7Ftl6OXK5AnksD4gfbOW/L+h+WPOourCiqLT48eMHJZlPbpVGleHLsRXGlUpVgtXM
T5FPv9ZM13bX1dc/akhq9GySe0b6bKq5qCW4Vb2Nru3j89oXse1WLwU7YB2TnaVdsa/su6V66Hs2
e1/23eg3HmAdWB6sH4obtnp9bgQ6MjlaNhY9bjkhMHE4Ofwm9633uwtTkKm+9/nToTPoWd7ZXx8G
57LnPRcufIR97FlM+oReOrE0tpy2YrxKvTqwFv8Zvc73hfrL3sbcZs/X6q173658x2yr/eDZQe7M
/ny2m7Hn/Ut1n2V/4+DFofvv/DMBC1AHEYCUQ/VhlLA9BBFSA/WEWICkiyyYQoryF3UPbSKdIQMF
4yhzCqspGxP7EmfNqbDTymfIeAf5bgoontsQyhARF20T1z7fISl1oUAaJmMkGyZXLD+ksK3EpCyh
YqTqrBasfk0jSTNd67Z2uk6qbqJerP5lAz9DdyMbtI2xnYmVqYWZqbm+hbKltJWANZsNhc2B7We7
KfsehwbHYqd7mHhsmLO3i4orreu8W6V7hIeRJ6fnptcL7zQfl4tSOHLcvG+TXwrey187gCcQGvgu
qDQ44JJ0CAjpDk0PcwgXDD+4PHAlO8I7UioKFTV6NTvaLUYoZutabWxQnNx1kutT8WUJlwnfBOvN
5cS6pKu3DJKZkxdTqlPD0jTSadKnM4pu4+8o3KW9u35vILMsK+m+V7ZWDnfOQe5kXtWDhHznAoWH
TA+3Hg0UlhTFFrs8Vi1hK/nypLb0UplcObS8qyK+0rCKoWqmuvCpX418LVnt27qi+tAGvUaOxh9N
fc9uN1u3sLbMtBa2XXwu9QL+YrA9+6VXh3QnUedYV+4rj26x7t2ett6oPpV+0v75gZbB7KGQYbPX
IiMkI3Ojz8ZSx90n5CapJj++qXkb+85yim/q5/ue6Qczd2azP+TNPZwvXqj62LI48GlpmXpFbfXm
2sK6/ZcvmxVb6d+f7rDszh1QHOX/j/cdeQJSAoB8gg9aUAGg1wpAVgIAPNEE71oFwJAcABMpANXt
A1A5HIB80ADH/sEGFIEDCAd3QTXoB4vgAMIAEYZoQZwgYZAMSAWkF/IJCodyQhWh9tAr0FzoC+gC
DAXjhxnA/GH3YK2wRTgZXBxuC78Gr4C/QyARYggHRCKiGbGOZEeikdeQTcivKH6UCyofNUPEQeRE
9IhojVic+ArxIAkPSRTJDKkSaT4ZERmO7C25JnkjhQBFPiUbZRYVG1UB9TnqOhp1mglanxOwE9l0
InQd9Lb0PxhSGcUYJ5jCmXmYR1iiWMVZl09ms5mz07D3clzn1ORCcfWeesQdd9qLx/CMGC8j7/7Z
Ob4O/kKB+HNegjpCAsJkwisir0SLxBLEfc/bSRhKKl0QlWKTJpfelfkkOyL3XL5S4ZFiplKScoLK
ddV4tRT1LI0nmi1aDdo1OpW6FXpV+g0GHYZjRkvGEJOTpgpmTuYJFk2Wn63ZbSxtM+yGHagcJZ0w
mFvYVudtVyE3H/enHodeut65Pts4I99KPI1/QMC7IMXgwhDa0Jxw1csrEbejFK5uxuTE6sXtx5fc
ME+EJ9Uk26SSplVnWN1hvLuXuXC/M+dRXly+50OdQqFixhJUKSg7rERVM9RI1tk2YJsuNke0pj2v
a1/sZHpl3fO4HznoOfxmVGe85432uyvvs2aaPkzNby9SL/GtyKyprWtuqH+V+Ma+jfgx87NqL2b/
j3/wAH3gC26BMtANFsD+P9nH/M5+JaQfsgxFQk9DVaFY6DVoMbQPugGjg0nD7GExsBLYa9gunAuu
A8fD78O74JsIVoQmIgCRjxhGQpCiSAwyA9mLgqKkUH6oMtQakQCRN1EV0S6xCvEt4gUSJZJcUgip
M2kPmSjZfXIi8iDyRQoLij5KFcpnVJJUddSS1A00cjTttDq0YyewJw7oMuml6d8yhDOyM7YzuTNT
MdezOLKSsD49acdGxtbA7sJBx9HJGczFx7V4qpE7+bQnj8aZM7xEvJtnJ/na+SsFcs4lC14VChb2
FnEQNRczEtc/byhhJml5wUbKVNpYRldWVU5GXkzhnOJZJW5lDhVuVR41YXV5DQNNrJantouOq66L
nqc+3iDSMNWoiOB7C6bEZiLmdhaplr3WcBtV2+t2fQ60jspOAZhi7LQLq6uVW677qqeUV7z37EVJ
XJrvFt7EvyaQJSg8eD7EKPR9eOQVzoi+KL9ojpi+2KDr3PFDN0ITzySNJ4el8qUNZwTfkbxHnfnl
fntOah4mX6Rg71FHUcpjhyfny6jKP1eOV7fXtNY1NKQ2+TWbtyo+F2kX6hDpkulG9+L7MwcHXiNG
lcbjJgffTk21TN+bvTLntKC+KLrEvcK8Rr/OuHHm6/lvets+O4m7tb+WfvsHO1ABWBAFckAjGAXr
ECIIJ0QWYkb4P5EAKYS0Q2Yg+1BWqAzUBhr++/QvwkhhwjAzWDisANYL24KzwtXgOHgW/BX8O4IL
YYSIQFQi5pEMSB1kJLKecPYFUB6oItQSET8RjqiOGBDrEGcSr5PokZSQUpDiSd+QqZBVkLOTp1IQ
U0RRAspIKiRVEjULdTGNLM0wrecJxIkCOjm6cfoABjqGOkY7JhKmWmY3FlaWUdbEkzpsJGx97Ikc
aE4mzlmu4lOJ3JdP+/K4nbHjtThryofmRwugz5kKmgpZCtuI2Io6iXmIh57Pl3h9ASLFJ20hEy1b
ITejQK2ooxSt3KlKqmalXqFJroXRfqyzpaekn2KwYqSCzjdBmHqaDVnIW5Zas9gk26HsQx1mnKQw
6divLuauLe78HlleFN4xPr9wAb6beB//5UDXoLlLjiGbYXmXbSMYI8eu3o2xiGWIG49PvaGfSJTU
mRySKpG2nHH/jvc90yzlbI5ckDed3/wwvdC32LBEvJS9nJJwupE1tHWnGyCNE88etkS2Wb2QfXm6
k6TrZ/d670r/x8HV4c2Rn+Mkk0xv6d51vvecOTnbOxeywPWx65Pb0t5K+Or2Z+v16g3I5vmvtlth
36K+X90O+GG7I/4T8bN9N2qPf2/ol/8+bD/1gOuQ9Cj/f+qlI/8ACHc9R0Lt9P/bvL0CjmPSECKT
+TjpGxB6IsK1hPM3PKoDfzM+0FjtmF3c1bWOGeuoqnPMIW4q+sfs4qeOPmYPR23DY3b2MTU+ZpzX
7/r2n7WU/+qd8Wp/NSFuJubHer8AtOkxe17U+avHOqv+3ZuPl77uscbdX+vv/oE70AOOAPOnziQo
AJLgw1keR9Q6khxx1P/v5u8cTKhBAVC5iLvk5+7q5s+hRKiynQU4tHwwggIcosLCUuB/AB9EIuTH
1bVnAAAACXBIWXMAAAsTAAALEwEAmpwYAAAgAElEQVR4Ae2dCbxP5dbHDxkylnmeCUnIlFxTEVJm
GtyGm27eW128KR+SV326hsoUSThyP2RWhiZziDKFkG4q83SICOFkeL/Oej3v9t//c/z3f9z7f9b+
+GzPXs96hr2e33+dtZ9hrQxXrlxJ0EslEI8SyBiPL6XvpBK4KoFMKgb3SODzzz9PSkqy9qdz5845
cuSAuHjx4scff1yyTpw4MX/+fEnnypWratWqFStWNKVOnjy5cuXKNm3aCGX37t379+9v2LChYUgt
ce7cuWzZspncBQsWtG7d2jx6MaGa20Wj9uuvvx44cGDJkiXDhg0jwXXp0iX6N2bMmH79+gFZ6Stg
HTBgwO8p14YNG5o3bz537lzzGgcPHnzttdfMIwzjx483j6klKNWxY0fJpdG+ffv26tUrNWav0FVz
u2iknnjiCXozb968ixcv9u/fX3p2+fLl6dOnDx8+/L333mvUqJEQCxUq1KNHD0lXqlRp1qxZ7dq1
k8fU7ijmTz/9tFSpUnXq1BGepUuX7tixo3r16uh1/jKg49esWVO/fn0UNmyp1eMhumputw8Wirxa
tWpt27Zdu3atMVqSk5P3plwbN26cMWNGkyZNrK/x22+/8XuQa/Xq1WQBXCrZt2/fhx9+2L59eyiz
Z8/mB8OPhF8RnPyEmFrgTtaECRPefPNNa4UeTavmdvvATZw48dFHH0WXA8rExETsE3q8Z8+ebt26
gXUS06ZNa9my5bFjx86ePUsWRsX58+e3b98uL4Ztkz17dgp26tRJLI3atWtj2GDUXLhwIU+ePJg0
N998M2xTpkxp0KABpYoWLXr69Gkp7um7gtvVw3f8+PFly5YdPnx45MiRaFZA2adPH3p82223LVy4
kET37t1RxoB7xIgRy5cvh/LWW28VKVJk4MCB8mJYLHwaAlZjjVB28+bNXbt2BdOYOvxBGD16NHpd
+OPprmaJq0cT4Hbp0uWrlAsDA53KjIq1x0OHDt26deukSZMGDRoETLny5ctnZZA0kyeLFi0i/eef
f3755ZdMsGDM3Hrrrdj3/GWYPHlypkyZ+ONgL+hpioLb1cMH8swMIB1F3Y4dO9ba4yxZsmBy9O7d
25jj1lyTbty48S233NK0aVM0NMxlypThw3HIkCF8O2Ln9OzZk5/NoUOHnnvuOVMkDhIZdIUyDkYx
wFfAFs+cOfNNN91k+E+dOpU7d+4MGTJAAQl8p2bNmtXkej2h4Pb6CGr/U5WAmiWpikYzvC4BnS1x
7wiOGjUKg1jmniPay8cee4y57Yg2EZPKFdwxEfuNG33nnXcGDx7M8gqfejfmDoHjs88+Y7YxhArc
W1TB7caxYVabqYyZM2cyJx3R/vEpyfJNvE4qqM0dUfAEU7kgm8WXSCM7Y8aMzHnL3qxgOur6Mgpu
dw2RQXaFChUi2jOQ/c0335w5cyaircS2cjVLYiv/61oH2djZc+bMKV++/HUZ4X7AGmFdk+0o4a7Y
XfXpPLeLxoMVFjayRnq7KftM2DrLZld583Xr1v30009ms7iLxBFyV1RzhyzC8FXA7o677rqrWLFi
4avST03soTXI9pMdRyS1ueNoMPVVrpeAau7r5eGOJywH9Gt4+8KWEnOwMrw1u7Y2Bbcbh4YNTMw9
s+OPHaph6V/+/Pk5aByWqjxUiYLbvYOFCY79zcwGl7WXPMqyC9N5kuBOGh4SPmmYmRVhvyv4tlaS
HtIKblePcsGCBdmDehXd13al0l2TxtIQNHNnpoVdKFykOXkAmzwCeo6fwcnl6leNQOcU3BEQalir
FE0MNME0aeoWhU0aIncuiKSFDqYNuFl9hM4F9LnC2i8PVKbg9sAgXdXbGTIAWcGxFdz0HiKABrui
tg24ocMJsrHduQviPfC24euigjt8soxwTYAVgIJyA26Bu2Ba0gJ0wbEBN/xAH3xHuIOuq17B7boh
sXYIgHIBX8G0aGVgyiNsJCSXNIAWlEMRcPMomvuqRZI5M/rbWnN6SCu4XT3KYk6AUfDKZX30ATTw
FXDLD4BcA24py93vqzLbSP1+s7xO9P/CXn+ruOk/AOWjED1tTfCIehZlTIKXJdeAG36UtGh0+aDk
kYtZF7+z5izF420wbiRmfREFt1UaLk2DVC46JwlrWgwPK7hFu8MMkTQM8jPgbgc3q0Xbtm3jvI9L
3zy0bim4Q5NfhEsLjqURa9qHglYGxKAZOnexQEiI5k7DLMHrWvHixSO9wzbCQkq1egV3qqJxQ4Z8
OEpPrGlDEaLgXiwTKKAZiljSory5c9nf6Ntvv33wwQft9PigKLhdPY5g1H7RY4hyRz2DZuERaxvb
Q3BMFnSAngJs/+BmZZ5Ntq4WQQidU3CHILyoFAW7ctGaNSGNX8u8OjNIGnyDZtHZPAJu0iS4c0Wl
vy5qJN29sItkH1hXRCtzh13S1nLWXGHgDsQFzdzR2AJ3UefWsnGfVs3t9iH20c08Wnssjz5EMI1N
ApvAWiDO3VowPaTT3Qt7a1BRzGI6Gw0tqOVRXkQScjdZwgwDCfltkPb5AXhLDsH1VjV3cHKLUimC
HwBQNnbLdyEJrAsf7KKSjYYGwTBA4RJYU4OxUqLUadc0o+B2zVDYOgJMf/nlFzAKUpnm41Gwmzdv
XlYcBe6EcQLxkit6GmbBt1Hb5FLQVn38ExTcLh1joHnnnXcKUgXHQJZLcAyFC4hbGUibS34SvBsJ
SfMb8HlVNPoff/xBLm35ZEH0oXjxUcHtllH7+uuv6YqgitAfJipkav3DwsaZfGq5dvqe7AdO3nK6
+qnKJosWjx49SnxACRFo6CSmTp2K61crxYtpBbcrRo2gN0TweOSRR3LmzBmhDm3Is+373D9Zwf2X
v/ylZs2aNEejZcqUIUyUaPFnn332yJEjEepGNKtVcEdT2v7bWrVqFU4X3n77bTz3rVixwsSoJpwk
0a8xP6QY8YVDOeR7a0Km+gmVlyQsYT8JoUII0geUieJH5fwRwLgH0GwyIX4au6n8d9RrVAV3jEfM
ILtVq1ZE+K1RowaAlj6x8QNHr+YRj2eEkAy9u5wXBtn2evg2JUg2PyF7lkcpCu5YDhzIxhoh3B7I
ph/16tUjVDtKFPXJ157ETeVDkMi/3FHkOPWT7vLhaE3wiBrmczPlOzOTzP2J+S6fmKS5+J0Qe5LL
/s6wYejHmWtMBbd9oKNEETt72LBhDzzwgDQJvFq0aEEadBL8eteuXXwyYjNUrFiRaQ00LspVZjbA
ukxgg2ZQCzShSyAy+HnE3qA2LBwQX6BAAaP+sT2IHezzhnGJbN5Rwe0z0NF7JL46O/JOnDhBJFW/
rYJXzF+ATi5BhPngI7Je4cKFDTM4NmlrIkVNZ6BmIaL4TS5ZJm0S/FRSq8rweDGh4I7ZqIEnPuwq
lCuXvHdv1l+PZ7yckHxrrsslSxb0FwRn8eLFzGmggP2epgH6oTg+3rlzZ4kSJWImiIg1rOCOmGgD
q3jn9u15Vq7Ks3lr5uSLZ6vcdqRJY7/gRuOiicU096kY+4So2LjcxlLfuHEjNoYw+ChjauDvAL8N
62xjoUKFWCpi/sSnzvh4VHB7aRzHfp146ujJLLsysgIP1vOWzrezwN7CmwnifiuvwYoMoc+MkYOZ
Du7N66H1mUnkN3DPPfcYYth9yZqa3ZBQcMd4FLJmy5acJcu5HNn/zPznedwCXpvVtncL1du0QKOD
yQcTUo7OlC5dGp7Sl0ol3JnARIrwM8f34siXT2c6W/5sKb4+T548aerhs5KvT8wbQ4n7hII7xkNc
vU6dBP4FcKURDkE+E7E6/vOf/+T/Lf/lDFe2Xj7lU6VM8+3fv59oOCbLin5DjJuEgtszQ1mlSpXS
bSpkvpy51LmiPp0W64JZPwyPIgWL+ORaH5lqNEue0JlwtObGWVrB7ZkBZWYQYyON7gJujG++EdPg
8cnyu6Djw+PdRwW3Z8YuDbOE9R3PvEYUO6rgjqKwr29K1hqvp6X1VLly5WbNmvnlCO+kB1+iYsT7
bctDRAV3zAYrEgDig9LRziemC33en98J0eDbtm3rQ/fio4LbM6N2wx8DG1bZT+LofcqVK2flX716
9cKFCwkIz/ZuK92jaQV3LAfuhx9+GD16dCA9YIGGoE2fffYZyzd2fjaCE8jdTg+Qwt4SONmQ+NFH
HwFuOcEQYFk3sym4Yzk67IW69957TQ84H2nSfhN8OIYr4h6ANkY/O2nx9crRsnnz5nE8x2/TXiQq
uGM5any6mb17KM4b+qQMF7J5Z44+3HHHHfLyaH0Bd2ofrLGUUQht+zn5HEJtWtSBBNjGDaqs25hk
i4iDKq6xsoeE34mj4uyeNZobm+eDDz7o0qXLtfri5H8Fd8wGkmM4GLgGYaH0A9udRfWHH344uEo4
vda+ffvgyrq5lILbzaMTaN/mzJkzduzYZcuWBVogffD9397f9PGycfuWbBeRGY+4fcOgXkzBHZTY
XFZIwe13QBTcfsXiMaKC2++AKbj9isVjRAW33wFTcPsVi8eICm6/AxZ+cLNxxxrXEL8COOjw2zZT
s37paROpUHxG+mVbsGCBX3p8ExXcfsc3/ODGlQwOQlkUkPY2bdo0ceJEe9t47rqhI1N7KSibN2+e
PHmyPQv/Hn379u3Vq5c9K+4pCm6/Qxx+cNMMO48HDBjAcT1rk4Dvk08+Wb9+vRA5qbp79+41a9bM
nTtXnBAsXbqUpTJyt2zZgnpGr8+ePVv4qeq7776bNGkSHjZMneyIWL58uXnELxmrbuYxXSUU3H6H
OyLgJiht//79n3nmGdMk+4br1KmDF7wZM2b89a9/hQ6gWZzjnpiYiHYH+p06dSKXLLQvZ/uqVasG
xHFUwOIZEGexmv0P6HupE1cbnTt3xpOBaWLChAn4cDKP6Sqh4PY73BEBNy3h45n7+PHjpdXPP/+8
atWqjRs3xs/5jz/+iPuYBg0acNqPO957Fy1atG7dOtJoYrQvzuxYlwbroHzUqFGobfj5bQwfPrxJ
kyZUSA0cdJ05c2alSpWkfu5WoBtiOkkAbrsnqnTy7mm8ZqTATZOo5DfeeGPPnj2k8cbL+Q5sZS5A
nJSUZPr00EMPcfoDK+W55577+eef+RngV+n06dPYNsKDG18MGCt2qbNu3brp89vRyM2aUM1tlYZJ
RxDcuJ97/fXXMb5pDLyy1x7Vi4t1TBS8OZrxYE8zS8dffPEFoK9Vq9bAgQPbtWsn6pyCKCQOhpQs
WdJ6DqV58+Z8pLKbgg1D5k3Sc8IIMz0Lwf7uEQQ3jT399NP169cnwR2Asl2YCx3McRLuhw4dQluT
27JlS3wMsFm5adOm7MfH2saA4cfAI+nevXsXLFjQp+ts7+Sn8tRTT4kTVJ/c9Pao4PY74lHdFYhL
JNw0MhLSFT4ooYhXab+dwzu1BO/ym6tEIwFMPow3+2lfw5A+E1E9iUNoOauUsTTSQDac8e0yxiqK
ENOoAN0VaJdhVMFtb14pYZGAy80S1t3QU2aGgAUKZgjkxZkxw/IkzToGX1CYo8a7vp3iVFaRtbmd
9kb5g5MA4JZFg+CKR7QU87ZMAHCgzrTCGki/fv3eSbk4zw+9Z8+ef/vb31jFI96VTBLYKaa4gwRC
0cvrEsC1A0POSUq3vQgLHcwcENOH2S3TNz4PcB5kHkFzsWLF5DT+iBEjWAmxUwyzo4RqbgeKwLWs
8o3uQrObiFOc6if0jxEds2EEOWGijOVkVqyhc/oTfxJ48SSNowuiRNgpprijhDObm+VD2f7hqA2X
MDOZIDFFXdKfMHZDNuew8SaMvh+C6x6TBHirEqRSg2y1sFaFJc2uIZbqmOq97777sE/wnG+Cx+Ix
i3hrLNL5UKw1BJ52Bm7Ww/HbEnjtruJEiAjUhIxxVd9C7wzKm2WB0OsJvQa2A0nAQb9VsY2CiUvx
s4xGZyPnk08+af7msGbH79P6fSwUv1XdkOgM3Kyoc92wUncyoBXYwYJDPXd2L530ir/8aBkBN1uD
2DiEUY6XC3l9LBYUPya4DyU44ajNHZzctFSQEmAPnKxD82nIVybuZO+//37mUpgfRH+ztZOpFZax
fSjBNeZMcwfXhpZSCRgJsDn0hRdeYN8b9gZ7KNiyz16MwYMHs60Idc68yvvvv89inw/FFHeUiOry
u6OehZ1ZzZKwizToCvkCJtaU1WMtWOeLn48iU6edYrICTKhZEqCglC2cEuCz3opsqmYHgRXZfilO
e6Dgdiox5feMBBTcnhkq7ahTCSi4nUpM+T0jAQW3Z4ZKO+pUAgpupxJTfs9IQMHtmaHSjjqVgILb
qcSU3zMSUHB7Zqi0o04loOB2KjHl94wEFNyeGSrtqFMJKLidSkz5PSMBBbdnhko76lQCCm6nElN+
z0hAwe2ZodKOOpWAgtupxJTfMxJQcHtmqLSjTiWg4HYqMeX3jAQU3J4ZKu2oUwkouJ1KTPk9IwGP
nX7/97//jUei4KSLt+9x48ZxTDi44j6lCEOFzzsfoj66SgJeAvfzzz9P9Jx69eoFJ0HcYuCcLizu
4HDug+/Jf/3rX8H1REtFRwLeADcOXHB2sWzZsjlz5hQoUCA40RAg6qWXXsKhUXDFraXwt6vhSqwC
cWfaAza3IJsofrNmzQoa2UgfJ3Q4HQ19GFasWEG0k9Dr0RoiLQG3a26QjTVCQDOiToaCbORIxHic
Y4QoUJAtzrBDrEeLR0ECrtbcYUQ2ogwR2TjnVWRHAZFhbMLVmnvIkCF4TMbAxZ2zxKEU98+lS5fG
nVyuXLnwA41jLqtXYn4PPMolRYywyOKCXxLQfcpibOAanfgExOHGE6nVqsYTKb8No7P5NmXuxdSs
CXdKwNXg/v7773GxhSvyEydO4LMZNBPMkijDxBcmgBDIxoYmkSdPHlzzE6xVMI2ggW9q4hZkA2uw
y535ExyK4qUO4OKcDsjCQNhLqqU2eYSN8ADG5zS+02nXJzJbas0pPYYScDW4RS6XL9/crm23vXsu
f/3N56VKZQB5okdRpeAPiKOhiRWflPX4D/fsabb6bsJhnSp89uwt5+84VoEaVpbacM/+GpkvZ7qQ
MXl1qW/r7ah25vSZlXnWn7t4rtymovxgcC4KoFHY6GMu0qCchN9RAdnMlJNL034ZlOgeCbgd3AA3
KenCylU7M1zJnPzn6YQEP/OA4BuNfq7YlZwFThQqWTj5TPKnZVcUP1mo6Il8R3OeWFl0fdFd+fP/
fuv8msuP5jpR6lyhWzLkOlM1uXhS0crnKqOVuQB02kMiDCh4wlmIOk+bX3PdIAG3gxtUlSuX7fz5
bejpO+/Mm4bILt10Ke/ZW9DQWXNm+T3f2ZZbGl7JdiVrtqx7Cx0uebFoQvaEizkuF/+jSJGshajk
ZI7T9x90sBhENwTZKHjsmV9//VViLKXRH82KuQTcDm4wzfx0zpw5sXHR4tbLR3Y3Xc6Y6dLViFiB
XFkuZs6QkMEvp7UJbA/R2dzR2WK6TJ06Fd/SErXebw1KdIkEXO18nlhYTJXkzp0bYYE5EZlJ8AmY
lJTEtyYmstjfwgYi9xY8XO5ECRB5PuOF3UUPVjlUnqz9uY5kvJSh0O9X95aQhd1sbBI+H/HyTygW
85loMC2NMgkopjbI5gOXKXOYJUvvrpWA28G9adMmQqgAaGAHarmwsDEJcF3OZyWzFihUiERa4VNP
5vKALDwQASgXzNwZAOhmdo8fA2H74GGmBVhjRh87doxJGOIPoZ7lg5JcM1uyb9++li1bEqdr7969
imzXotmnY243SwSXPp3mESDu2rUL/IFjIM4MiZgu3MUaBpcGyqY4WVmzZuURBP/+++8wsMdw+/bt
4F5MjtQmSSiiyDZi9ErC7eC2A9QuWRQtGAXoZKHjBfEyUe2jueEExLBBN2aJvUIfCsxbtmzhB6A6
20cyLn90NbhZiZw2bRqaFd0slgbA5cIKL1WqFLhPIyIwIAaUXCzTlChRghpAJ1ca4wHcKUUIUNYp
SdMQdg41yIIl4crVzk5Dei7McrXNjbxYZMG2Rg2jks0F8rCwyRXwAVlQbr4FhU1kDTRZ0cRooR4o
PAqdO6WY3RMQQ6cUaMZuoSp+SFDkwv5B348cOZLTCaasJjwhAVdrbiTYo0cPPhaBHYADf4CPBJcA
UdKwgWC+CEEhPFjVABe9LujkE5DthOCbIkKhFEV4ZG83cyAQ4aeslALulJU0d3KrVasWrvM7nsBE
3HTS7ZobCwEUAjKROGkuAAeIoXCXBBTokj516hT8MnkC/aGHHuLITKNGjeDnLwCKmVw4yYLCXSq/
WlGGDKShmEsYuPODYYKFhF4ekoDbNTcrOE6laQ9wyHQhl6mHn4FJayKOJRD/w4yNoWiOYwSn8Wrx
D24sDTGy05CCZsWlBNxuloQudLvm5ugD6/bWmjt37iz2D/TFixc//vjjksva/vz58yXNfEvVqlUr
VqxoCqada9jsCb4HmJq00+0UDjW3bt3aTldKIBJIj5qbPX1MZuMlYtiwYSS4+AGIsMaMGdOvX7+V
K1fKI6vxAwYMYC2Ti/MKzZs3nzt3rhFr2rmGzSdx8ODBjh07+hDtj3Spb9++vXr1smcpJVAJmJmB
eE0w37dx40b72wHTTp06WengqXz58rNnz0aRC52FyVq1ahmeDz744JFHHjGPqeUyfc5BfXybCCdz
kd9++62kOTVHJZUrV169ejUUph3RzYaTHSzUCcOPP/74wAMP/OMf/6A/pjlNOJVA/Gtuu1mS2u8e
Xc6Udtu2bdeuXWvsFtaJQCcXv5AZM2Y0adLEWtyeu3v3bioBpuxFkXUfasNRlpRioyz9YZD4EuA3
UKdOHRZQqZb9jzCsX78eTLMginafMGHCm2++aW1L004lEP82d+AflBMnTnz00UfRpoAyMTER+wRp
ssG1W7duYJ0EewHYG8hqEbPvZAFTey6l+IMg5kTt2rUxXXyGhOOe4L5BgwY4GMKIb9y4MQx///vf
WasiAdyHDx8uRVgclYTeg5NAugB3IFOBYAuPVocPH2alHc0KKPv06YNMcQjIAU0S3bt3B5SAe8SI
EXgIgjJo0CB7LogEoDIY5G7evJk0FQqFX44kuGOrYO5PnjyZNFiXvxXsNTAMmghRAmqW/J8AAW6X
Ll2+SrkwiAEZkypW4Q4dOnTr1q2TJk0C01gaXNY1eZPbpk2bRYsWUZD1fHwJoZuZhzl06BAUoIzW
ZweBQLxVq1ac7UdPv/3225gobBCAh1VSa6OaDkUC8Q/uAM0SbBIzA4hAu3btOnbsWKtk2ZiFrdK7
d29jjvvNvf3224EsByywvGHmc5aVfwzx++67D9dZZcuW5WcD1jG+69evz7nmZikXRJ+FVWvlmg5O
Am7fWxLcW1lLoV/RshUqXHXzELWLoxLsRbEuHnHskiM/0gGsFL5E5dgECawm1HnU+pZ+Gop/mQao
ucM75OzQ8qnQIBs6tocgm7TZqevDr4+hSyBdmCWBfFCGLkqtwW0SiH9wBz7P7bax0f6EKIH4B3dM
zJIQR0WLh0UC6QLcapaEBSueqyT+wa1miedAGa4Oxz+41SwJF1Y8V0+6ALeaJZ7DZVg6HOfgRm0j
JutiSlikppV4QgLpAtyquT2BxbB3Ms7BzdckIlNwhx03nqgwzsGtZoknUBihTqYLcKvmjhB6XF5t
nINbzRKX4y+i3YtzcKtZElH0uLzyOAe3aG493uJyFEaoe3EObl2ejBBuPFFt/INbvyZjDkROSf/w
ww/WbuzYsePjjz8WJwJChwEXLhL3QijfffcdTi+ImWEt6Cgd5+DWXVOO0BAJZhwM4amLGOSmcnyz
vPjii5z9q169ungWePbZZ1944YVVq1bhrQ5X63D27NmTQHZLly6tUaOGzw/D1HPjBOf54vjCQwMO
ueP4BV3+auPHj+fsM5Dl/LV0FZTjcEvSKG/OTePdjiPVnP+H+Oqrr7700kugmQgt+AiAgiONJ554
Qvid3uNcc2Nzq1lyYw0XMQ78feJj8a677jIt4NQF93HyiK8YgomCbE6UoqRxLIo6L168OC40cF0k
O4LuvfdeiKa4o0Scg1vNEkdoCDszbuLQ3NZq0TUSnwj/FkS8wEEXJ//xHYe/F7Q1WMfpBX68TLAA
nBcEbXY7O/0+bty4oH9G1jeMWhr/T3yjYL1FrUWXNISzQjBECNko94dZV8IY4bMl7XYJDffggw++
8sorBHXhwxEvMXx0litXDk8vGCG4oTOuufBtFER0DWndGbhp3vqFm/YLuCEXKw2fCjjKcUNnotkH
vGny5x5/V9FslLYAt9URl9/WcSmKt1GMaZwqwkDocZxvye8Bg7tmzZrk8nEpZXFwh2Mjv/XcmOjU
SFd+T0gA13CjRo1ySVdxL2o+KLFGChYsiKM507effvqpSpUq/I2F8u677z722GPY4vDs3LkTtc1f
3ddff90wO0o409w3/q0oh0ogTQmgsI8ePcokiXBhW+OeDgS3aNECAxKzG8fNeJYbPHgwntELFSrE
TMv777+fZpWpZsa/O7VUXz2uM/iSq1u37j//+U8PvSXKW741pc+obeYHMa6CfoU4ny0JWi5aMPoS
sCKb1nG2GAqyqUHBHf1B1BajJAEFd5QErc1EXwLhBzerqdOnTzdvwoQrDt3NozVBxDrrY4BpKvz6
66/tzJhoeH0nXIE9SynpUwLhB/euXbuYzSEklwh006ZNTAPZhRtgxDp7QWb7JdSGNYvfCTtsmECl
3Q4dOlizNJ1uJRB+cCNKdsYQvtEn1hEr4Z988gkBu0TWxDIl3sCaNWsImSfnZdhdwCQRuYSrQz2D
V6LmCT9VsY5FyA7mPs1QMT8qsWmgUM+TTz7JWi6BJNl2wy/HsGki3UogIuBm70v//v2feeYZI1Z7
WDoAzYQ8d2JxoN2BPutV7N+lCKHACI3HkhUQl4B31hh2Uuf27duJFmn2LRCm4+WXXyaLgiwBaAgO
I/n0nIgIuBEoO3S5s+NRhH0i9W0AAA8VSURBVEvwJAlLx84BNviCP+J3MUXPXSIksVOMNJr41KlT
hOtlm68EvGOZDbUNv8SwkzCQ1MCc/8yZMytVqmQdPJANnV04AQaftpbVdPxJIFLgRlKo5DfeeIMd
XqRNWDrMZROWTqTJ1hmim2KlsB2Mjer8DNhpwHw+to0wEPAOA8YoaYjUyQoFBzeEQe5YLCCbQHsa
LN0qlvScjiC4S5Qowa4AjG/kaw9LZyLWFSlShC1gX3zxBaBnxXXgwIHt2rXzCXhH1C/rIV9OdvCR
SrQxc0aDHQtgesqUKWSl5+HUd7dKIILgppmnn36agHQk7GHp0MQSsY5cIpcSIYmdjZjO7DrE2iau
LqtTJuAd22isnSbNXj8iOD711FMY6zwOGTKEj0gsGXaQcfH16cOvj+lQAlHdW+ITlo4PShOxzq/o
7QHv/LIp0S4BL+4tsb9FiJSo7gr0CUuHpWEi1vl9DXvAO79sSlQJ+JVAZM0Sv00qUSUQHQkouKMj
Z20lBhJQcMdA6NpkdCSg4I6OnLWVGEhAwR0DoWuT0ZGAgjs6ctZWYiABBXcMhK5NRkcCUZ3njs4r
xXErrMKygzKQF4STjZPsMQ6E2c7TsGHDEM8v2uuMPiWqK5TRf714ahEvTWyKZJsN23Ju+F5sds+Z
Myf7dm7IaWegLDuCnn/+eXuWtyg3FpO33ideeyvIxs8v23UCeUc4OZqEm7JAmH14aMLqJ9sn10OP
anN7YLDY/IjODhzZobwS9gzeVkOpwT1lVXO7Zyz89wRk48YX9zqO3HlyEKRAgQL+a0ydeuDAAc74
pZ7vsRwFt6sHLDhk80oc83P6YnGGbF5fzRKnGIgeP/vdxRpxpLOD61/8IRs5qOYODgzRKCVHLtgV
PHXq1Ii2h9OBChUqRLSJmFSu4I6J2ANtFGTjiT1Q7mD5OMAabFFXl1Nwu3p4TOfwp2WCDRhiiAnO
jkjcmRDrcW1xBbdrh+a6juF1CP8WHMy7jhraA5HyypcvH1odri6t4Hb18Ph0Dl0bLv2NGxmmC33q
j7NHBbeXBhSX1aw7Cr5JG69dpHkNHAFwYWlIdEIsGU6pkoYoLylu6yASMYciVm8ZXpJCwH1VcAcs
KhcwAkcsE/Q320sE3IJvATdpAbf0VOBLEYjcuQTc5PIDoIa4j9Cp4HYBZp10QWBKCRKipIG7wBSK
AJcERC75XhQ6d4NmkM0ldCeNe4xXwe2xAZPugkvUMNgV/W00NxaLQS1Q5oITouAYuEtxeCgi0Pfk
+wfWaQV3YHJyGZeBKf0yM3rAHRCLOpf+Cri5y6MpBQ+lzKPLXi5s3VFwh02U0axINLFpkUeUMWAV
m9vkAmLSfFnCCcSNzQ0zl2puI0BNuEUCgNjvJROFds1Nv4E4lxXcaZgluJDGFaNb3jaEfqjmDkF4
MSoKTGk5Ba7X3UA8y/ViikjXSHOJhoZV5gRJ8DPgMli3vseZM2d++eUX/EpbiR5NK7g9OnD/323R
4vIsYAe4PJIG2ULhDgVTRNhIwIOfUXm03gk5xFR6EHvBrZW4JK3gdslABNQNcBwIH2ygGcND8E0R
gbhR1Vct7pSpQHuFhAmwxnsJpDnX8ii4XTs0/jsmepo7SAWy3MXqMHRJCJrF/oZCXUKRSkmTxeWz
mM/RSUKy4P7Yf9teoyq4PTZi4JIeC1J98GrNsvL4GCdkQUFz298crGOXx4dNwtv5eUP7OyvFPRIQ
Neyjp+keKlyyJCFAFzbBsfWXgM4G3+55qQj1RMEdIcFGqlqreha8CkXUM63aUQuD5AonPCkmSfzj
W8EdKRS6sF6De4G7C3sY3i7F/9+m8Mor5rX5GCQ8ih0id3mUTpI2CSnFo1Hw4JsiMX+diHZANXdE
xRvmyvng40i8GBViN3PHpM6VKxdr7NxJM3stj7RNLiAWTh5Jy6Okw9w591Wn4HbfmKTSI+atWRUH
31aVLLzoYGY5uMCuJMA6Shq6mCKipFOwfVVhE78cumSl0lo8kBXc3hhFfK4C6zJlyhiFDTTR0zxy
SULu0M3yDWlR1YJjc7daL9b3//777+GfPn26lUiasHJt27Yly4fu8kcFt0sHiADhgwYNMqEMWRK/
YUdFZ8Pmd13dXvz9stPO3XT+v3962vD/9ttvNWvWfOedd7Jlyya/BCm1atUqFnfKli1rr8TNFAW3
G0cHZBPnO3/+/BGN9l3mbInkjFd3wxqfrqY5/hoQ3Zyz8ehsXPYQuVwMGzcKK/U+KbhTl02McgTZ
RAQfPXr0W2+9tWTJEtMR9uuVK1dOHvfv38/xddkjZRgcJZgpuzkhYUnCEj5SCUluLcsfgT179uzb
tw9879y501j5Vh73pxXc7hojkH3//feDWpCNDY2pjccpg62zZ8/WqlVLHrGAQR4TI7yAWMPQScg9
8LeiyLFjx/zysw4Psv1meYKo4HbRMAmyRWeDbHqG3xw2WJ86dQrlyhmCc+fOLV++HIWKC22YwSXf
jrBhMwi+MSeggG8u0tjNQuE3AEXMDynCndALWD7Mq9CiXQqFCxc+cuSIne4hioLbRYPVqlUro7Ol
W/Xr1zf9w+MUZgkWMCYEqAXQYB1dLtawnCXjDoj/+OMPSmGxgHjAzV3Qzw8GyObNmzd79uwY0/J7
QG3zOzGtSCIOkM2LKLh9hjWWj1999VX37t0TExMD6QSBRAh5g2VcqlQpO39ycjJ2s53OfIid6EOR
vYFMm/jQPfeo4HbXkNWtW/fozp051q7LtfvAxexZjteulaPmXRUqVbL3EuyioTt27GidszNs+Bak
KvPoKIHr5NSscEf1xJxZwR3zIfDtwJ+nT2dJOppt/4GLOW6+qeLvJ48f9+W49swsOHYzTxgYWCNi
ZkgiT548xYoVYzkGq/oa+1V/a+aXgKGCxbJ7924WhgwD+r506dL58uVTcBuZaCLaEsByAJrYJJOO
TM+97eb8WfJii1+dFqyU6fyVC5c3X5DTNCCbFXu+R6V/8FNK0qAcewYTv1mzZqb3fLMSqMQ8ej2h
mtt1I5irSNGEqlUu5M13OWuWTCVLFile3N5FZkvQzajqZ0s8cbmYbXNflQRgKqWYSdya+8ci5wsU
SM57xx13oNeFzjcl84zWSXR7K16nKLhdN4KVa9dK4F/KlVqMVMwGpj6Y88YTsVHG1jcR1P78889C
TErYZ801aXS5Fd9Mv+TIkUNMHcPj3YSC25Njx7Qgqhe7YmOBbXecui3Hpex+X4NVHqvV4ZfHSlSz
xCoNTcdGAizKYJOcPHmy7onqsemBF1pVze2FUbL1URZZli1bhl1hy7xKMDa339x0QlRwe3Kg2fXB
tAabqFKzOqyWdIhvyPwgkzMyzxhiVVEuruCOssDD0xxfk4EAjkkVRyhn9R47nt0sppcg+9133737
7rut0+Em1+UJBbfLByik7j388MNBlF+3bp2UEmRjAi1cuNCs/gRRYayKXF3ZilXb2q6PBPjTz3I6
0yA+dL+PLM2wyw/bmulqOwN7oWQ3rD3rhhQmBFn9adSo0ZgxYwTZ5kDQDcu6ikE1t6uGI4GlGXbt
0SeUDkZFnTp1otM/LHhMHVHPTMLws/E6spGbgjs64Am0FbZ8tGzZUrhnz54daLGQ+fgtseFWqpk7
d+6CBQsqVaqENRLKSZ+QOxVqBWqWhCrBMJbnr79szjZ1Rs3SBdxcpt0KFSps2bLF08jmXRTcZkBj
n2DzU2rz1tHsHKZ/lSpVAjT9o9kxp20puJ1KTPk9IwH1FeiZodKOOpWAgtupxJTfMxJQcHtmqLSj
TiWg4HYqMeX3jAQU3J4ZKu2oUwkouJ1KTPk9IwEFt2eGSjvqVAK6/O5UYhHkZzPJ/PnzpQG2PXE+
smLFirjRmTdvnrVVXGVzbvKjjz4yRPZOtW/fXh7ZGbJy5co2bdrII84bcJnZsGFDw5xagv1SeC4m
l42vOG1j75TX/fKo5k5trGNAB4UDBgxgox/Xhg0bcCjMNg+Ir7766gHLBfjw4tenTx+h7T9w4NCR
I5yAl3/7Dx4c8NprOJuSf+s2bBg3frzJTS1BqQ4dO5J79ty56jVqrN+4ceIHH7Tv0MHwmwoNxeUJ
OqyaOwYgTqNJHIn06NFDGNi6NGvWrL59++I2rX///tZSqGcO4wiRHSH/vynEynR9GsX86aefchbB
7DRcunTpjh078LWJXl+8eDE6Hj9VsD3x5JMvv/wypavcfvvBgwdx7nN9TZ55UnC7a6g4H7B37176
hPOGGTNmdOjQgTSbs1esWCEdZXNVvXr1SONL7ZtvviEBsitWqsReWWHgjiUz41roj7UpPAC3RfPm
z3brtvqrr94cMuSjjz9my+G/J00Cx//Tv3+3//ovNmyxcYp705SLSugGZ+xl/62p2VsJBXcsx8tH
4/K4e88eIJiUlMQOqmnTprH9devWrb8ePz55yhTpKB6k7q5XD87jJ06MfvddIb7YqxenzvD4yiM+
0wgD8v327ZKF6cIWqImJiZ06derVqxfEOrVrY+pg+bBpm5/Ex3Pn4vEVtg+nTCGCgpQC2S1btBg/
YYJY4RA9Fg4npcMKbhnNmN2t+CZ92223fbFwIb3p0b37hx9+2KJlS4j470ucONF0EQr/iEj24dSp
htjvlVf4CuTxzbfewoz518CBkoVh88mCBej+2tfOPdDE5s2bu3btCqbHvvfe2rVrR40ebY2sgMP5
tm3ajBg50kQRMa14K6EflC4dr7eHDkVnT5o0KcD+DRw06Ju1a/mHG0t7kdZt2ixetAg6H6Nffvkl
8zDYPPwRmDtvHj+bKZMny4ljGPBy36Z1a/5QeB3ZvItqbjsSXEHhoMCExMSHHnxw1uzZ27ZtK2vx
xfrOqFFMETrqZePGjefNndusaVOw+3Lv3hxlB81dHnts/LhxxGkYOmxY0aJFyXr+ueeg8xHZuVMn
qR/0W5W6o0Zjzqz7uUMdAjESgquFsuaKglGLLU60EObIzd9rThnnzp1bfJLwQcnnrPvPAjMFab+M
JI0YoSi47YJyRvEQuM2LGXAbiocSgYPb06/poRHRrsZAAqq5fYXuVzH4MkXyWfVNuKSrH5ThkqTW
Ew0J8GHA6iyfCqxh8QnBqhMfDHxIMB+PW3Hmf8zEPL1RcEdjSLSN0CXAsuuuXbsOHz7MbGYatfG5
DNbZScaU6P8CbEB5Oe1D92wAAAAASUVORK5CYII=

--Apple-Mail-27-946412721
Content-Type: text/plain;
	charset=ISO-8859-1;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: quoted-printable



On Jan 21, 2009, at 5:24 PM, Dunn, Jeffrey H. wrote:

> Thomas,
>
> We would be happy to see any results you may have concerning =20
> application behavior during PMTUD.
>
> Best Regards,
>
> Jeffrey Dunn
> Info Systems Eng., Lead
> MITRE Corporation.
> (301) 448-6965 (mobile)
>
> -----Original Message-----
> From: Thomas Peterson [mailto:thomasp@iol.unh.edu]
> Sent: Wednesday, January 21, 2009 3:00 PM
> To: Dunn, Jeffrey H.
> Cc: R=E9mi Denis-Courmont; ipv6@ietf.org; Huang, Frank; Sherman, Kurt =20=

> T.; Liou, Chern; steve_eiserman@uscourts.gov; ipv6-bounces@ietf.org; =
v6ops@ops.ietf.org=20
> ; Grayeli, Parisa
> Subject: Re: End System PMTUD behavior question
>
> Hi Jeffrey,
>
> This is Thomas Peterson from the InterOperability Laboratory at UNH.
>
> We have done extensive testing in this area and would be happy to work
> with you off line to examine this scenario.
>
> If you would like we can even set up your test topology in our lab.
>
> Thanks,
> Tom
>
> On Jan 21, 2009, at 2:44 PM, Dunn, Jeffrey H. wrote:
>
>> R=E9mi,
>>
>> I agree with you assertions concerning "ping" versus TCP; however, I
>> am looking for some concrete documentation or experiences.
>>
>> Best Regards,
>>
>> Jeffrey Dunn
>> Info Systems Eng., Lead
>> MITRE Corporation.
>> (301) 448-6965 (mobile)
>>
>>
>> -----Original Message-----
>> From: R=E9mi Denis-Courmont [mailto:rdenis@simphalempin.com]
>> Sent: Wednesday, January 21, 2009 2:33 PM
>> To: ipv6@ietf.org
>> Cc: Dunn, Jeffrey H.; ipv6-bounces@ietf.org; v6ops@ops.ietf.org;
>> Sherman, Kurt T.; Liou, Chern; steve_eiserman@uscourts.gov; Huang,
>> Frank; Grayeli, Parisa
>> Subject: Re: End System PMTUD behavior question
>>
>> Le mercredi 21 janvier 2009 20:56:23 Dunn, Jeffrey H., vous avez
>> =E9crit :
>>> Colleagues,
>>>
>>> We have been performing some PMTUD tests and have found that
>>> different
>>> operating systems handle PMTUD differently. Specifically, we found
>>> that the
>>> "ping" application behaves in the following way when the PMTU is
>>> set to
>>> 1280 and a 1500 octet ICMPv6 echo request is sent to that routed
>>> path. The
>>> hosts we tested:
>>
>> I'm afraid ping applications are not representative of what the
>> operating
>> system IP stacks do. Besides, there are no standards regarding the
>> behavior
>> of "ping" in case of Path MTU problems; it's really up to the
>> implementor of
>> each "ping" whether to report an error or to transparently fragment.
>>
>>
>> The behavior of real transport protocols, such as TCP, DCCP and SCTP
>> is more
>> interesting when it comes to evaluating operating systems and their =20=

>> IP
>> stacks.
>>
>> --=20
>> R=E9mi Denis-Courmont
>> http://www.remlab.net/
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>


--Apple-Mail-27-946412721
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--Apple-Mail-27-946412721--

From ipv6-bounces@ietf.org  Thu Jan 22 14:36:15 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AE5A628C17F; Thu, 22 Jan 2009 14:36:15 -0800 (PST)
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 CE15828C17F; Thu, 22 Jan 2009 14:36:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.941
X-Spam-Level: 
X-Spam-Status: No, score=-5.941 tagged_above=-999 required=5 tests=[AWL=0.658,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 mlkWVckr+6CS; Thu, 22 Jan 2009 14:36:06 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 975BC3A68F4; Thu, 22 Jan 2009 14:36:06 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.37,308,1231113600"; d="scan'208";a="34631134"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 22 Jan 2009 22:35:49 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n0MMZnhn016391;  Thu, 22 Jan 2009 17:35:49 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n0MMZnb7019953; Thu, 22 Jan 2009 22:35:49 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 22 Jan 2009 17:35:48 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: End System PMTUD behavior question
Date: Thu, 22 Jan 2009 17:35:47 -0500
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0632C194@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <3C6F21684E7C954193E6C7C4573B762701D3DD69E6@IMCMBX1.MITRE.ORG>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: End System PMTUD behavior question
Thread-Index: Acl7+fSDtCRQmHdATNy7UebOW+92QAACmYbgAASrC5AAK66ZwA==
References: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG> <B00EDD615E3C5344B0FFCBA910CF7E1D0632C176@xmb-rtp-20e.amer.cisco.com> <3C6F21684E7C954193E6C7C4573B762701D3DD69E6@IMCMBX1.MITRE.ORG>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Dunn, Jeffrey H." <jdunn@mitre.org>
X-OriginalArrivalTime: 22 Jan 2009 22:35:48.0876 (UTC) FILETIME=[C60964C0:01C97CE1]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1327; t=1232663749; x=1233527749; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=shemant@cisco.com; z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco. com> |Subject:=20RE=3A=20End=20System=20PMTUD=20behavior=20quest ion |Sender:=20 |To:=20=22Dunn,=20Jeffrey=20H.=22=20<jdunn@mitre.org>; bh=Qzoi189D6imjvqRk++mdfuCQgwFrFC9omNmNjcd5JOY=; b=Z4DK5i5XNny7d/ptLA/pVPKBOdliEtHb5zAgQfM7e3AFjU1P+ciPDMFTIh 3IddZdg0Uf7qXzM2qfo7rLW4sXv5sQM94t6xc7cuetcn0I8jCMbNN1MykC/T NQL1IRto1c;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); 
Cc: ipv6-bounces@ietf.org, "Sherman, Kurt T." <ksherman@mitre.org>, 6man mailing list <ipv6@ietf.org>, "Liou, Chern" <csliou@mitre.org>, steve_eiserman@uscourts.gov, "Huang, Frank" <fhuang@mitre.org>, v6ops@ops.ietf.org, "Grayeli, Parisa" <pgrayeli@mitre.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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org Jeffrey,

Both IPv4 and IPv6 standards recommend not to fragment.  So the first
impact on the system behavior for host receiving an PTB message is to
try and not fragment.  I have not paid attention to older RFC's.  I am
working off of RFC 4821 that recommends a host keep "conceptual"
variables in cache at the IP layer and all other layers of code on the
host may access this cache to get the current value of the MTU to be
used by host.  See following text from RFC 4821.

[Furthermore, the natural mechanism to 
share Path MTU information between concurrent or subsequent connections 
is a path information cache in the IP layer. The various 
Packetization Protocols need to have the means to access and update 
the shared cache in the IP layer. This memo describes PLPMTUD in 
terms of its primary subsystems without fully describing how they 
are assembled into a complete implementation.]

Also see section 5 of RFC 4821.

What UNH has tested for current host behavior and so have you is because
host are following older PMTU RFCs like 1981.  Also, I agree with you on
RFC 1981 that host may fragment if there is no easy means for the host's
layers to pass MTU information back and forth.  My 2 cents is for new
hosts to follow RFC 4821 and not fragment packets.

Thanks

Hemant

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Thu Jan 22 15:55:35 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0070D3A6806; Thu, 22 Jan 2009 15:55:35 -0800 (PST)
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 D633D3A6806; Thu, 22 Jan 2009 15:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.202
X-Spam-Level: 
X-Spam-Status: No, score=-5.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
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 6JGxB-8QThAZ; Thu, 22 Jan 2009 15:55:32 -0800 (PST)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 857E73A677C; Thu, 22 Jan 2009 15:55:32 -0800 (PST)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n0MNsgw2022833; Fri, 23 Jan 2009 01:54:44 +0200
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 23 Jan 2009 01:54:44 +0200
Received: from vaebe108.NOE.Nokia.com ([10.160.244.69]) by vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 23 Jan 2009 01:54:40 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: End System PMTUD behavior question
Date: Fri, 23 Jan 2009 01:54:39 +0200
Message-ID: <808F2ECE7425024994976AC3D44BDCF4C8B900@vaebe108.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: End System PMTUD behavior question
thread-index: Acl7+fSDtCRQmHdATNy7UebOW+92QAACmYbgAASrC5AAK66ZwAAI127Y
References: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG><B00EDD615E3C5344B0FFCBA910CF7E1D0632C176@xmb-rtp-20e.amer.cisco.com><3C6F21684E7C954193E6C7C4573B762701D3DD69E6@IMCMBX1.MITRE.ORG> <B00EDD615E3C5344B0FFCBA910CF7E1D0632C194@xmb-rtp-20e.amer.cisco.com>
From: <Peter.Hunt@nokia.com>
To: <shemant@cisco.com>, <jdunn@mitre.org>
X-OriginalArrivalTime: 22 Jan 2009 23:54:40.0026 (UTC) FILETIME=[CA0597A0:01C97CEC]
X-Nokia-AV: Clean
Cc: fhuang@mitre.org, ksherman@mitre.org, ipv6@ietf.org, csliou@mitre.org, steve_eiserman@uscourts.gov, ipv6-bounces@ietf.org, v6ops@ops.ietf.org, pgrayeli@mitre.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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0174434914=="
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org This is a multi-part message in MIME format.

--===============0174434914==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C97CEC.C9F8E0DD"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C97CEC.C9F8E0DD
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hemant,
=20
Forgive me if I've misunderstood, but it sounds like you're saying that =
we should require protocols or applications above IP to always send data =
in messages small enough to avoid IP fragemntation.
=20
I agree it makes sense for a higher layer to use the PMTU information in =
IP's cache when it can. Expecting TCP to use the PMTU is perfectly =
reasonable, as it's already chopping up a byte stream into packets. For =
protocols which are already packetized, though, I think it's less =
advantageous to burden them (or the application using them) with the =
problem of fragmentation and reassembly, to avoid IP fragmentation.
=20
For example, if a user does a "ping -s 1500" to a destination whose PMTU =
is 1280, the only way to avoid IP fragmentation is for the ping =
application to split the data into multiple messages, or for IPCMPv6 to =
do so. Either way, you have to introduce some way to identify them as =
"ping fragments" and reassemble them in order. That will require changes =
to the ICMPv6 protocol, I think. Furthermore, you're no longer really =
doing a "ping 1500", but two pings of 1280 and 220 bytes, respectively.
=20
In the case of an application which sends records in single UDP frames, =
to avoid fragmentation is must split its messages into MTU-sized =
chuncks, and come up with a way at the destination to identify and =
reassemble the chunks in order. This seems a bit unreasonable, given =
that IPv6 has a perfectly good mechanism to do this already.
=20
So I think the behaviour observed by Thomas during his testing is =
correct. I don't think ping or ICMPv6 should reduce the ICMP message =
size to avoid IP fragmentation.
=20
Peter Hunt
Software Engineer
Nokia S&S.
=20

------_=_NextPart_001_01C97CEC.C9F8E0DD
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>RE: End System PMTUD behavior =
question</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.6001.18183" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText26585 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" color=3D#000000 =
size=3D2>Hemant,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>Forgive me if I've =
misunderstood, but it sounds like you're saying that we should require =
protocols or applications above IP to always send data in messages small =
enough to avoid IP fragemntation.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>I agree it makes =
sense for a higher layer to use the PMTU information in IP's cache when =
it can. Expecting TCP to use the PMTU is perfectly reasonable, as it's =
already chopping up a byte stream into packets. For protocols which are =
already packetized, though, I think it's less advantageous to burden =
them (or the application using them) with the problem of fragmentation =
and reassembly, to avoid IP fragmentation.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>For example, if a =
user does a "ping -s 1500" to a destination whose PMTU is 1280, the only =
way to avoid IP fragmentation is for the ping application to split the =
data into multiple messages, or for IPCMPv6 to do so. Either way, you =
have to introduce some way to identify them as "ping fragments" and =
reassemble them in order. That will require changes to the ICMPv6 =
protocol, I think.&nbsp;Furthermore,&nbsp;you're no longer really doing =
a "ping 1500", but two pings of 1280 and 220 bytes, =
respectively.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>In the case of an =
application which sends records in single UDP frames, to avoid =
fragmentation is must split its messages into MTU-sized chuncks, and =
come up with a way at the destination to identify and reassemble the =
chunks in order. This seems a bit unreasonable, given that IPv6 has a =
perfectly good mechanism to do this already.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>So I think the =
behaviour observed by Thomas during his testing is correct. I don't =
think ping or ICMPv6 should reduce the ICMP message size to avoid IP =
fragmentation.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>Peter =
Hunt</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>Software =
Engineer</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>Nokia =
S&amp;S.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV></DIV></BODY></HTML>
------_=_NextPart_001_01C97CEC.C9F8E0DD--

--===============0174434914==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--===============0174434914==--

From ipv6-bounces@ietf.org  Thu Jan 22 17:02:03 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A3E83A6981; Thu, 22 Jan 2009 17:02:03 -0800 (PST)
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 C0ADD3A696D; Thu, 22 Jan 2009 17:02:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
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 I8mTD7OUalO0; Thu, 22 Jan 2009 17:02:00 -0800 (PST)
Received: from mx.isc.org (mx.isc.org [IPv6:2001:4f8:0:2::1c]) by core3.amsl.com (Postfix) with ESMTP id C1D853A6981; Thu, 22 Jan 2009 17:01:57 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "farside.isc.org", Issuer "ISC CA" (verified OK)) by mx.isc.org (Postfix) with ESMTPS id A3174114050; Fri, 23 Jan 2009 01:01:15 +0000 (UTC) (envelope-from Mark_Andrews@isc.org)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "drugs.dv.isc.org", Issuer "ISC CA" (not verified)) by farside.isc.org (Postfix) with ESMTP id E8F22E6072; Fri, 23 Jan 2009 01:01:14 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.3/8.14.3) with ESMTP id n0N119J0038463; Fri, 23 Jan 2009 12:01:10 +1100 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <200901230101.n0N119J0038463@drugs.dv.isc.org>
To: Peter.Hunt@nokia.com
From: Mark Andrews <Mark_Andrews@isc.org>
Subject: Re: End System PMTUD behavior question 
In-reply-to: Your message of "Fri, 23 Jan 2009 01:54:39 +0200." <808F2ECE7425024994976AC3D44BDCF4C8B900@vaebe108.NOE.Nokia.com> 
Date: Fri, 23 Jan 2009 12:01:09 +1100
Cc: ipv6-bounces@ietf.org, csliou@mitre.org, ipv6@ietf.org, ksherman@mitre.org, steve_eiserman@uscourts.gov, fhuang@mitre.org, v6ops@ops.ietf.org, pgrayeli@mitre.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/pipermail/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org In message <808F2ECE7425024994976AC3D44BDCF4C8B900@vaebe108.NOE.Nokia.com>, Pet
er.Hunt@nokia.com writes:
> Hemant,
> =20
> Forgive me if I've misunderstood, but it sounds like you're saying that =
> we should require protocols or applications above IP to always send data =
> in messages small enough to avoid IP fragemntation.
> =20
> I agree it makes sense for a higher layer to use the PMTU information in =
> IP's cache when it can. Expecting TCP to use the PMTU is perfectly =
> reasonable, as it's already chopping up a byte stream into packets. For =
> protocols which are already packetized, though, I think it's less =
> advantageous to burden them (or the application using them) with the =
> problem of fragmentation and reassembly, to avoid IP fragmentation.
> =20
> For example, if a user does a "ping -s 1500" to a destination whose PMTU =
> is 1280, the only way to avoid IP fragmentation is for the ping =
> application to split the data into multiple messages, or for IPCMPv6 to =
> do so. Either way, you have to introduce some way to identify them as =
> "ping fragments" and reassemble them in order. That will require changes =
> to the ICMPv6 protocol, I think. Furthermore, you're no longer really =
> doing a "ping 1500", but two pings of 1280 and 220 bytes, respectively.
> =20
> In the case of an application which sends records in single UDP frames, =
> to avoid fragmentation is must split its messages into MTU-sized =
> chuncks, and come up with a way at the destination to identify and =
> reassemble the chunks in order. This seems a bit unreasonable, given =
> that IPv6 has a perfectly good mechanism to do this already.
> =20

	For the record.  DNS servers just tell the kernel to fragment
	at network mtu for UDP/IPv6 and ensure that DF is off for
	UDP/IPv4.

	DNS clients don't usually generate packets big enough to
	be a issue.  If they do need to send a big (> 512) message
	they usually just switch straight to TCP to avoid having
	to probe the server to see how big a UDP message it will
	handle.

> So I think the behaviour observed by Thomas during his testing is =
> correct. I don't think ping or ICMPv6 should reduce the ICMP message =
> size to avoid IP fragmentation.
> =20
> Peter Hunt
> Software Engineer
> Nokia S&S.
> =20
> 
> ------_=_NextPart_001_01C97CEC.C9F8E0DD
> Content-Type: text/html;
> 	charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> 
> <HTML dir=3Dltr><HEAD><TITLE>RE: End System PMTUD behavior =
> question</TITLE>=0A=
> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
> <META content=3D"MSHTML 6.00.6001.18183" name=3DGENERATOR></HEAD>=0A=
> <BODY>=0A=
> <DIV id=3DidOWAReplyText26585 dir=3Dltr>=0A=
> <DIV dir=3Dltr><FONT face=3D"Courier New" color=3D#000000 =
> size=3D2>Hemant,</FONT></DIV>=0A=
> <DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>=0A=
> <DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>Forgive me if I've =
> misunderstood, but it sounds like you're saying that we should require =
> protocols or applications above IP to always send data in messages small =
> enough to avoid IP fragemntation.</FONT></DIV>=0A=
> <DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
> <DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>I agree it makes =
> sense for a higher layer to use the PMTU information in IP's cache when =
> it can. Expecting TCP to use the PMTU is perfectly reasonable, as it's =
> already chopping up a byte stream into packets. For protocols which are =
> already packetized, though, I think it's less advantageous to burden =
> them (or the application using them) with the problem of fragmentation =
> and reassembly, to avoid IP fragmentation.</FONT></DIV>=0A=
> <DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
> <DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>For example, if a =
> user does a "ping -s 1500" to a destination whose PMTU is 1280, the only =
> way to avoid IP fragmentation is for the ping application to split the =
> data into multiple messages, or for IPCMPv6 to do so. Either way, you =
> have to introduce some way to identify them as "ping fragments" and =
> reassemble them in order. That will require changes to the ICMPv6 =
> protocol, I think.&nbsp;Furthermore,&nbsp;you're no longer really doing =
> a "ping 1500", but two pings of 1280 and 220 bytes, =
> respectively.</FONT></DIV>=0A=
> <DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
> <DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>In the case of an =
> application which sends records in single UDP frames, to avoid =
> fragmentation is must split its messages into MTU-sized chuncks, and =
> come up with a way at the destination to identify and reassemble the =
> chunks in order. This seems a bit unreasonable, given that IPv6 has a =
> perfectly good mechanism to do this already.</FONT></DIV>=0A=
> <DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
> <DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>So I think the =
> behaviour observed by Thomas during his testing is correct. I don't =
> think ping or ICMPv6 should reduce the ICMP message size to avoid IP =
> fragmentation.</FONT></DIV>=0A=
> <DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>=0A=
> <DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>Peter =
> Hunt</FONT></DIV>=0A=
> <DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>Software =
> Engineer</FONT></DIV>=0A=
> <DIV dir=3Dltr><FONT face=3D"Courier New" size=3D2>Nokia =
> S&amp;S.</FONT></DIV>=0A=
> <DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV></DIV></BODY></HTML>
> ------_=_NextPart_001_01C97CEC.C9F8E0DD--
> 
> --===============0174434914==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 
> --===============0174434914==--
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Thu Jan 22 20:28:10 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76E9F3A6A1D; Thu, 22 Jan 2009 20:28:10 -0800 (PST)
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 DE2663A6816; Thu, 22 Jan 2009 20:28:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.094
X-Spam-Level: 
X-Spam-Status: No, score=-6.094 tagged_above=-999 required=5 tests=[AWL=0.505,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 qPnrS6DSh5MS; Thu, 22 Jan 2009 20:28:04 -0800 (PST)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 319333A68F7; Thu, 22 Jan 2009 20:28:04 -0800 (PST)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0N4Rkew007704;  Thu, 22 Jan 2009 23:27:47 -0500
Received: from imchub2.MITRE.ORG (imchub2.mitre.org [129.83.29.74]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0N4Rks0007698;  Thu, 22 Jan 2009 23:27:46 -0500
Received: from IMCMBX1.MITRE.ORG ([129.83.29.204]) by imchub2.MITRE.ORG ([129.83.29.74]) with mapi; Thu, 22 Jan 2009 23:27:46 -0500
From: "Dunn, Jeffrey H." <jdunn@mitre.org>
To: "Mark_Andrews@isc.org" <Mark_Andrews@isc.org>, "Peter.Hunt@nokia.com" <Peter.Hunt@nokia.com>
Date: Thu, 22 Jan 2009 23:27:45 -0500
Subject: RE: End System PMTUD behavior question 
Thread-Topic: End System PMTUD behavior question 
Thread-Index: Acl89idt4hgVSkIuTk67SSBj8+G5bAAHFQyA
Message-ID: <3C6F21684E7C954193E6C7C4573B762701D3DD7186@IMCMBX1.MITRE.ORG>
References: Your message of "Fri, 23 Jan 2009 01:54:39 +0200." <808F2ECE7425024994976AC3D44BDCF4C8B900@vaebe108.NOE.Nokia.com> <200901230101.n0N119J0038463@drugs.dv.isc.org>
In-Reply-To: <200901230101.n0N119J0038463@drugs.dv.isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "ipv6-bounces@ietf.org" <ipv6-bounces@ietf.org>, "Sherman, Kurt T." <ksherman@mitre.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "Liou, Chern" <csliou@mitre.org>, "steve_eiserman@uscourts.gov" <steve_eiserman@uscourts.gov>, "Huang, Frank" <fhuang@mitre.org>, "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, "Grayeli, Parisa" <pgrayeli@mitre.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/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org Mark,

Could you elaborate on what you mean by "DNS servers just tell the kernel t=
o fragment at network mtu for UDP/IPv6 and ensure that DF is off for UDP/IP=
v4."  What is the "network MTU?" Also, to which implementations of DNS serv=
er are you referring?

Best Regards, =

=A0 =

Jeffrey Dunn =

Info Systems Eng., Lead =

MITRE Corporation.
(301) 448-6965 (mobile)

-----Original Message-----
From: Mark_Andrews@isc.org [mailto:Mark_Andrews@isc.org] =

Sent: Thursday, January 22, 2009 8:01 PM
To: Peter.Hunt@nokia.com
Cc: shemant@cisco.com; Dunn, Jeffrey H.; Huang, Frank; Sherman, Kurt T.; ip=
v6@ietf.org; Liou, Chern; steve_eiserman@uscourts.gov; ipv6-bounces@ietf.or=
g; v6ops@ops.ietf.org; Grayeli, Parisa
Subject: Re: End System PMTUD behavior question =



In message <808F2ECE7425024994976AC3D44BDCF4C8B900@vaebe108.NOE.Nokia.com>,=
 Pet
er.Hunt@nokia.com writes:
> Hemant,
> =3D20
> Forgive me if I've misunderstood, but it sounds like you're saying that =
=3D
> we should require protocols or applications above IP to always send data =
=3D
> in messages small enough to avoid IP fragemntation.
> =3D20
> I agree it makes sense for a higher layer to use the PMTU information in =
=3D
> IP's cache when it can. Expecting TCP to use the PMTU is perfectly =3D
> reasonable, as it's already chopping up a byte stream into packets. For =
=3D
> protocols which are already packetized, though, I think it's less =3D
> advantageous to burden them (or the application using them) with the =3D
> problem of fragmentation and reassembly, to avoid IP fragmentation.
> =3D20
> For example, if a user does a "ping -s 1500" to a destination whose PMTU =
=3D
> is 1280, the only way to avoid IP fragmentation is for the ping =3D
> application to split the data into multiple messages, or for IPCMPv6 to =
=3D
> do so. Either way, you have to introduce some way to identify them as =3D
> "ping fragments" and reassemble them in order. That will require changes =
=3D
> to the ICMPv6 protocol, I think. Furthermore, you're no longer really =3D
> doing a "ping 1500", but two pings of 1280 and 220 bytes, respectively.
> =3D20
> In the case of an application which sends records in single UDP frames, =
=3D
> to avoid fragmentation is must split its messages into MTU-sized =3D
> chuncks, and come up with a way at the destination to identify and =3D
> reassemble the chunks in order. This seems a bit unreasonable, given =3D
> that IPv6 has a perfectly good mechanism to do this already.
> =3D20

	For the record.  DNS servers just tell the kernel to fragment
	at network mtu for UDP/IPv6 and ensure that DF is off for
	UDP/IPv4.

	DNS clients don't usually generate packets big enough to
	be a issue.  If they do need to send a big (> 512) message
	they usually just switch straight to TCP to avoid having
	to probe the server to see how big a UDP message it will
	handle.

> So I think the behaviour observed by Thomas during his testing is =3D
> correct. I don't think ping or ICMPv6 should reduce the ICMP message =3D
> size to avoid IP fragmentation.
> =3D20
> Peter Hunt
> Software Engineer
> Nokia S&S.
> =3D20
> =

> ------_=3D_NextPart_001_01C97CEC.C9F8E0DD
> Content-Type: text/html;
> 	charset=3D"iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> =

> <HTML dir=3D3Dltr><HEAD><TITLE>RE: End System PMTUD behavior =3D
> question</TITLE>=3D0A=3D
> <META http-equiv=3D3DContent-Type content=3D3D"text/html; charset=3D3Duni=
code">=3D0A=3D
> <META content=3D3D"MSHTML 6.00.6001.18183" name=3D3DGENERATOR></HEAD>=3D0=
A=3D
> <BODY>=3D0A=3D
> <DIV id=3D3DidOWAReplyText26585 dir=3D3Dltr>=3D0A=3D
> <DIV dir=3D3Dltr><FONT face=3D3D"Courier New" color=3D3D#000000 =3D
> size=3D3D2>Hemant,</FONT></DIV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT size=3D3D2></FONT>&nbsp;</DIV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT face=3D3D"Courier New" size=3D3D2>Forgive me if I'=
ve =3D
> misunderstood, but it sounds like you're saying that we should require =
=3D
> protocols or applications above IP to always send data in messages small =
=3D
> enough to avoid IP fragemntation.</FONT></DIV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT face=3D3D"Courier New" size=3D3D2></FONT>&nbsp;</D=
IV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT face=3D3D"Courier New" size=3D3D2>I agree it makes=
 =3D
> sense for a higher layer to use the PMTU information in IP's cache when =
=3D
> it can. Expecting TCP to use the PMTU is perfectly reasonable, as it's =
=3D
> already chopping up a byte stream into packets. For protocols which are =
=3D
> already packetized, though, I think it's less advantageous to burden =3D
> them (or the application using them) with the problem of fragmentation =
=3D
> and reassembly, to avoid IP fragmentation.</FONT></DIV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT face=3D3D"Courier New" size=3D3D2></FONT>&nbsp;</D=
IV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT face=3D3D"Courier New" size=3D3D2>For example, if =
a =3D
> user does a "ping -s 1500" to a destination whose PMTU is 1280, the only =
=3D
> way to avoid IP fragmentation is for the ping application to split the =
=3D
> data into multiple messages, or for IPCMPv6 to do so. Either way, you =3D
> have to introduce some way to identify them as "ping fragments" and =3D
> reassemble them in order. That will require changes to the ICMPv6 =3D
> protocol, I think.&nbsp;Furthermore,&nbsp;you're no longer really doing =
=3D
> a "ping 1500", but two pings of 1280 and 220 bytes, =3D
> respectively.</FONT></DIV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT face=3D3D"Courier New" size=3D3D2></FONT>&nbsp;</D=
IV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT face=3D3D"Courier New" size=3D3D2>In the case of a=
n =3D
> application which sends records in single UDP frames, to avoid =3D
> fragmentation is must split its messages into MTU-sized chuncks, and =3D
> come up with a way at the destination to identify and reassemble the =3D
> chunks in order. This seems a bit unreasonable, given that IPv6 has a =3D
> perfectly good mechanism to do this already.</FONT></DIV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT face=3D3D"Courier New" size=3D3D2></FONT>&nbsp;</D=
IV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT face=3D3D"Courier New" size=3D3D2>So I think the =
=3D
> behaviour observed by Thomas during his testing is correct. I don't =3D
> think ping or ICMPv6 should reduce the ICMP message size to avoid IP =3D
> fragmentation.</FONT></DIV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT face=3D3D"Courier New" size=3D3D2></FONT>&nbsp;</D=
IV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT face=3D3D"Courier New" size=3D3D2>Peter =3D
> Hunt</FONT></DIV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT face=3D3D"Courier New" size=3D3D2>Software =3D
> Engineer</FONT></DIV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT face=3D3D"Courier New" size=3D3D2>Nokia =3D
> S&amp;S.</FONT></DIV>=3D0A=3D
> <DIV dir=3D3Dltr><FONT size=3D3D2></FONT>&nbsp;</DIV></DIV></BODY></HTML>
> ------_=3D_NextPart_001_01C97CEC.C9F8E0DD--
> =

> --=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D0174434914=3D=3D
> Content-Type: text/plain; charset=3D"us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> =

> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> =

> --=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D0174434914=3D=3D--
-- =

Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Thu Jan 22 20:37:17 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D9D3C3A6816; Thu, 22 Jan 2009 20:37:17 -0800 (PST)
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 7C9A93A6816; Thu, 22 Jan 2009 20:37:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.459
X-Spam-Level: 
X-Spam-Status: No, score=-0.459 tagged_above=-999 required=5 tests=[AWL=-1.848, BAYES_00=-2.599, FRT_STOCK2=3.988]
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 sxL07dZ6JgPn; Thu, 22 Jan 2009 20:37:15 -0800 (PST)
Received: from mx.isc.org (mx.isc.org [IPv6:2001:4f8:0:2::1c]) by core3.amsl.com (Postfix) with ESMTP id BE5563A67F7; Thu, 22 Jan 2009 20:37:12 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "farside.isc.org", Issuer "ISC CA" (verified OK)) by mx.isc.org (Postfix) with ESMTPS id 5BA65114028; Fri, 23 Jan 2009 04:36:49 +0000 (UTC) (envelope-from Mark_Andrews@isc.org)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "drugs.dv.isc.org", Issuer "ISC CA" (not verified)) by farside.isc.org (Postfix) with ESMTP id B256BE6074; Fri, 23 Jan 2009 04:36:48 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.3/8.14.3) with ESMTP id n0N4akbE042009; Fri, 23 Jan 2009 15:36:46 +1100 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <200901230436.n0N4akbE042009@drugs.dv.isc.org>
To: "Dunn, Jeffrey H." <jdunn@mitre.org>
From: Mark Andrews <Mark_Andrews@isc.org>
Subject: Re: End System PMTUD behavior question 
In-reply-to: Your message of "Thu, 22 Jan 2009 23:27:45 CDT." <3C6F21684E7C954193E6C7C4573B762701D3DD7186@IMCMBX1.MITRE.ORG> 
Date: Fri, 23 Jan 2009 15:36:46 +1100
Cc: "Peter.Hunt@nokia.com" <Peter.Hunt@nokia.com>, "ipv6-bounces@ietf.org" <ipv6-bounces@ietf.org>, "Sherman, Kurt T." <ksherman@mitre.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "Liou, Chern" <csliou@mitre.org>, "steve_eiserman@uscourts.gov" <steve_eiserman@uscourts.gov>, "Huang,  Frank" <fhuang@mitre.org>, "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, "Grayeli, Parisa" <pgrayeli@mitre.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/pipermail/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org In message <3C6F21684E7C954193E6C7C4573B762701D3DD7186@IMCMBX1.MITRE.ORG>, "Dun
n, Jeffrey H." writes:
> Mark,
> 
> Could you elaborate on what you mean by "DNS servers just tell the kernel t=
> o fragment at network mtu for UDP/IPv6 and ensure that DF is off for UDP/IP=
> v4."  What is the "network MTU?" Also, to which implementations of DNS serv=
> er are you referring?

	Cut-and-pasted from BIND's bsd socket implementation.

	Mark

#ifdef IPV6_USE_MIN_MTU        /* RFC 3542, not too common yet*/
                /* use minimum MTU */
                if (sock->pf == AF_INET6) {
                        (void)setsockopt(sock->fd, IPPROTO_IPV6,
                                         IPV6_USE_MIN_MTU,
                                         (void *)&on, sizeof(on));
                }
#endif

#if defined(IP_MTU_DISCOVER) && defined(IP_PMTUDISC_DONT)
                /*
                 * Turn off Path MTU discovery on IPv4/UDP sockets.
                 */
                if (sock->pf == AF_INET) {
                        int action = IP_PMTUDISC_DONT;
                        (void)setsockopt(sock->fd, IPPROTO_IP, IP_MTU_DISCOVER,
                                         &action, sizeof(action));
                }
#endif
#if defined(IP_DONTFRAG)
                /*
                 * Turn off Path MTU discovery on IPv4/UDP sockets.
                 */
                if (sock->pf == AF_INET) {
                        int off = 0;
                        (void)setsockopt(sock->fd, IPPROTO_IP, IP_DONTFRAG,
                                         &off, sizeof(off));
                }
#endif

 
> Best Regards,=20
> =A0=20
> Jeffrey Dunn=20
> Info Systems Eng., Lead=20
> MITRE Corporation.
> (301) 448-6965 (mobile)
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Thu Jan 22 22:04:33 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B3DC53A68C4; Thu, 22 Jan 2009 22:04:33 -0800 (PST)
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 84C8F3A689C for <ipv6@core3.amsl.com>; Thu, 22 Jan 2009 22:04:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035,  BAYES_00=-2.599]
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 RmxT-iyoN4rz for <ipv6@core3.amsl.com>; Thu, 22 Jan 2009 22:04:30 -0800 (PST)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id 0AA753A6801 for <ipv6@ietf.org>; Thu, 22 Jan 2009 22:04:29 -0800 (PST)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id n0N63JwZ005027; Fri, 23 Jan 2009 08:03:19 +0200
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id n0N63Ir8005023; Fri, 23 Jan 2009 08:03:18 +0200
Date: Fri, 23 Jan 2009 08:03:18 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Peter.Hunt@nokia.com
Subject: RE: End System PMTUD behavior question
In-Reply-To: <808F2ECE7425024994976AC3D44BDCF4C8B900@vaebe108.NOE.Nokia.com>
Message-ID: <alpine.LRH.2.00.0901230751120.4544@netcore.fi>
References: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG><B00EDD615E3C5344B0FFCBA910CF7E1D0632C176@xmb-rtp-20e.amer.cisco.com><3C6F21684E7C954193E6C7C4573B762701D3DD69E6@IMCMBX1.MITRE.ORG> <B00EDD615E3C5344B0FFCBA910CF7E1D0632C194@xmb-rtp-20e.amer.cisco.com> <808F2ECE7425024994976AC3D44BDCF4C8B900@vaebe108.NOE.Nokia.com>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="1589707168-1135482102-1232690599=:4544"
X-Virus-Scanned: ClamAV 0.94.2/8893/Thu Jan 22 22:18:43 2009 on otso.netcore.fi
X-Virus-Status: Clean
Cc: csliou@mitre.org, ipv6@ietf.org, ksherman@mitre.org, steve_eiserman@uscourts.gov, fhuang@mitre.org, v6ops@ops.ietf.org, pgrayeli@mitre.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/pipermail/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>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org   This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--1589707168-1135482102-1232690599=:4544
Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8BIT

On Fri, 23 Jan 2009, Peter.Hunt@nokia.com wrote:
> For example, if a user does a "ping -s 1500" to a destination whose PMTU is 1280, the only way to avoid IP fragmentation is for the ping
> application to split the data into multiple messages, or for IPCMPv6 to do so. Either way, you have to introduce some way to identify them
> as "ping fragments" and reassemble them in order. That will require changes to the ICMPv6 protocol, I think. Furthermore, you're no longer
> really doing a "ping 1500", but two pings of 1280 and 220 bytes, respectively.

FWIW, what Remi said, different ping programs probably do this 
differently.  And good ones allow you to do exactly what you want 
(this is from Linux)

        -M hint
               Select Path MTU Discovery strategy.  hint may be either _do_ (prohibit fragmentation, even local one), _want_ (do PMTU
               discovery, fragment locally when packet size is large), or _dont_ (do not set DF flag).

When I use ping to figure out Path MTU issue, I usually have to run 
tcpdump on the side to be 100% sure how ping is actually behaving, 
because additionally, there's also PMTU caching on the local host. 
Some older versions also didn't support '-M do' properly for IPv6.

So there are quite a few things that could lead to non-deterministic 
behaviour.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
--1589707168-1135482102-1232690599=:4544
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--1589707168-1135482102-1232690599=:4544--

From ipv6-bounces@ietf.org  Fri Jan 23 04:06:27 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3DCBC3A6861; Fri, 23 Jan 2009 04:06:27 -0800 (PST)
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 EB5A63A6843; Fri, 23 Jan 2009 04:06:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.095
X-Spam-Level: 
X-Spam-Status: No, score=-4.095 tagged_above=-999 required=5 tests=[AWL=-1.484, BAYES_00=-2.599, FRT_STOCK2=3.988, RCVD_IN_DNSWL_MED=-4]
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 6I6cyXMhLCzo; Fri, 23 Jan 2009 04:06:24 -0800 (PST)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 358013A6861; Fri, 23 Jan 2009 04:06:23 -0800 (PST)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0NC65vs013166;  Fri, 23 Jan 2009 07:06:06 -0500
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0NC65gC013160;  Fri, 23 Jan 2009 07:06:05 -0500
Received: from IMCMBX1.MITRE.ORG ([129.83.29.204]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Fri, 23 Jan 2009 07:06:05 -0500
From: "Dunn, Jeffrey H." <jdunn@mitre.org>
To: "Mark_Andrews@isc.org" <Mark_Andrews@isc.org>
Date: Fri, 23 Jan 2009 07:06:03 -0500
Subject: RE: End System PMTUD behavior question 
Thread-Topic: End System PMTUD behavior question 
Thread-Index: Acl9FDkLNonOErpYTFKHM4HeUN959AAPPtMg
Message-ID: <3C6F21684E7C954193E6C7C4573B762701D3DD71AA@IMCMBX1.MITRE.ORG>
References: Your message of "Thu, 22 Jan 2009 23:27:45 CDT." <3C6F21684E7C954193E6C7C4573B762701D3DD7186@IMCMBX1.MITRE.ORG> <200901230436.n0N4akbE042009@drugs.dv.isc.org>
In-Reply-To: <200901230436.n0N4akbE042009@drugs.dv.isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "Peter.Hunt@nokia.com" <Peter.Hunt@nokia.com>, "ipv6-bounces@ietf.org" <ipv6-bounces@ietf.org>, "Sherman, Kurt T." <ksherman@mitre.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "Liou, Chern" <csliou@mitre.org>, "steve_eiserman@uscourts.gov" <steve_eiserman@uscourts.gov>, "Huang, Frank" <fhuang@mitre.org>, "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, "Grayeli, Parisa" <pgrayeli@mitre.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/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org Mark,

Fair enough, it appears the short answer to which implementation you know o=
f is BIND (I assume 9.x). With respect to IPV6_USE_MIN_MTU, I thought the v=
alue for this was 1280. If so, this simply circumvents PMTUD and uses the I=
Pv6 minimum MTU.

Best Regards, =

=A0 =

Jeffrey Dunn =

Info Systems Eng., Lead =

MITRE Corporation.
(301) 448-6965 (mobile)


-----Original Message-----
From: Mark_Andrews@isc.org [mailto:Mark_Andrews@isc.org] =

Sent: Thursday, January 22, 2009 11:37 PM
To: Dunn, Jeffrey H.
Cc: Peter.Hunt@nokia.com; shemant@cisco.com; Huang, Frank; Sherman, Kurt T.=
; ipv6@ietf.org; Liou, Chern; steve_eiserman@uscourts.gov; ipv6-bounces@iet=
f.org; v6ops@ops.ietf.org; Grayeli, Parisa
Subject: Re: End System PMTUD behavior question =



In message <3C6F21684E7C954193E6C7C4573B762701D3DD7186@IMCMBX1.MITRE.ORG>, =
"Dun
n, Jeffrey H." writes:
> Mark,
> =

> Could you elaborate on what you mean by "DNS servers just tell the kernel=
 t=3D
> o fragment at network mtu for UDP/IPv6 and ensure that DF is off for UDP/=
IP=3D
> v4."  What is the "network MTU?" Also, to which implementations of DNS se=
rv=3D
> er are you referring?

	Cut-and-pasted from BIND's bsd socket implementation.

	Mark

#ifdef IPV6_USE_MIN_MTU        /* RFC 3542, not too common yet*/
                /* use minimum MTU */
                if (sock->pf =3D=3D AF_INET6) {
                        (void)setsockopt(sock->fd, IPPROTO_IPV6,
                                         IPV6_USE_MIN_MTU,
                                         (void *)&on, sizeof(on));
                }
#endif

#if defined(IP_MTU_DISCOVER) && defined(IP_PMTUDISC_DONT)
                /*
                 * Turn off Path MTU discovery on IPv4/UDP sockets.
                 */
                if (sock->pf =3D=3D AF_INET) {
                        int action =3D IP_PMTUDISC_DONT;
                        (void)setsockopt(sock->fd, IPPROTO_IP, IP_MTU_DISCO=
VER,
                                         &action, sizeof(action));
                }
#endif
#if defined(IP_DONTFRAG)
                /*
                 * Turn off Path MTU discovery on IPv4/UDP sockets.
                 */
                if (sock->pf =3D=3D AF_INET) {
                        int off =3D 0;
                        (void)setsockopt(sock->fd, IPPROTO_IP, IP_DONTFRAG,
                                         &off, sizeof(off));
                }
#endif

 =

> Best Regards,=3D20
> =3DA0=3D20
> Jeffrey Dunn=3D20
> Info Systems Eng., Lead=3D20
> MITRE Corporation.
> (301) 448-6965 (mobile)
-- =

Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Fri Jan 23 06:36:24 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 158EA3A6AA5; Fri, 23 Jan 2009 06:36:24 -0800 (PST)
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 186A93A6A2E for <ipv6@core3.amsl.com>; Fri, 23 Jan 2009 06:36:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.819
X-Spam-Level: 
X-Spam-Status: No, score=-5.819 tagged_above=-999 required=5 tests=[AWL=0.780,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 LvuPI96S9rMQ for <ipv6@core3.amsl.com>; Fri, 23 Jan 2009 06:36:21 -0800 (PST)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id E1E8D3A69FA for <ipv6@ietf.org>; Fri, 23 Jan 2009 06:36:20 -0800 (PST)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0NEa2OZ000920 for <ipv6@ietf.org>; Fri, 23 Jan 2009 09:36:03 -0500
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0NEa2ij000914;  Fri, 23 Jan 2009 09:36:02 -0500
Received: from IMCMBX1.MITRE.ORG ([129.83.29.204]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Fri, 23 Jan 2009 09:36:02 -0500
From: "Dunn, Jeffrey H." <jdunn@mitre.org>
To: Pekka Savola <pekkas@netcore.fi>, "Peter.Hunt@nokia.com" <Peter.Hunt@nokia.com>
Date: Fri, 23 Jan 2009 09:36:01 -0500
Subject: RE: End System PMTUD behavior question
Thread-Topic: End System PMTUD behavior question
Thread-Index: Acl9IGzTCda24YBvSU2ZWaibZ9epxgARzCxg
Message-ID: <3C6F21684E7C954193E6C7C4573B762701D3DD72F0@IMCMBX1.MITRE.ORG>
References: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG><B00EDD615E3C5344B0FFCBA910CF7E1D0632C176@xmb-rtp-20e.amer.cisco.com><3C6F21684E7C954193E6C7C4573B762701D3DD69E6@IMCMBX1.MITRE.ORG> <B00EDD615E3C5344B0FFCBA910CF7E1D0632C194@xmb-rtp-20e.amer.cisco.com> <808F2ECE7425024994976AC3D44BDCF4C8B900@vaebe108.NOE.Nokia.com> <alpine.LRH.2.00.0901230751120.4544@netcore.fi>
In-Reply-To: <alpine.LRH.2.00.0901230751120.4544@netcore.fi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "Sherman, Kurt T." <ksherman@mitre.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "Liou, Chern" <csliou@mitre.org>, "steve_eiserman@uscourts.gov" <steve_eiserman@uscourts.gov>, "Huang, Frank" <fhuang@mitre.org>, "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, "Grayeli, Parisa" <pgrayeli@mitre.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/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org Pekka,

Good point.  We use Wireshark to capture the send/receive sequence on the h=
ost. In addition, we reboot the machine between tests to ensure the PMTU ca=
che is cleared, since we have show that, once learned, the host will immedi=
ately send fragmented ICMPv6 echo requests within the PMTU size.

Best Regards, =

=A0 =

Jeffrey Dunn =

Info Systems Eng., Lead =

MITRE Corporation.
(301) 448-6965 (mobile)

-----Original Message-----
From: Pekka Savola [mailto:pekkas@netcore.fi] =

Sent: Friday, January 23, 2009 1:03 AM
To: Peter.Hunt@nokia.com
Cc: shemant@cisco.com; Dunn, Jeffrey H.; Huang, Frank; Sherman, Kurt T.; ip=
v6@ietf.org; Liou, Chern; steve_eiserman@uscourts.gov; ipv6@ietf.org; v6ops=
@ops.ietf.org; Grayeli, Parisa
Subject: RE: End System PMTUD behavior question

On Fri, 23 Jan 2009, Peter.Hunt@nokia.com wrote:
> For example, if a user does a "ping -s 1500" to a destination whose PMTU =
is 1280, the only way to avoid IP fragmentation is for the ping
> application to split the data into multiple messages, or for IPCMPv6 to d=
o so. Either way, you have to introduce some way to identify them
> as "ping fragments" and reassemble them in order. That will require chang=
es to the ICMPv6 protocol, I think.=A0Furthermore,=A0you're no longer
> really doing a "ping 1500", but two pings of 1280 and 220 bytes, respecti=
vely.

FWIW, what Remi said, different ping programs probably do this =

differently.  And good ones allow you to do exactly what you want =

(this is from Linux)

        -M hint
               Select Path MTU Discovery strategy.  hint may be either _do_=
 (prohibit fragmentation, even local one), _want_ (do PMTU
               discovery, fragment locally when packet size is large), or _=
dont_ (do not set DF flag).

When I use ping to figure out Path MTU issue, I usually have to run =

tcpdump on the side to be 100% sure how ping is actually behaving, =

because additionally, there's also PMTU caching on the local host. =

Some older versions also didn't support '-M do' properly for IPv6.

So there are quite a few things that could lead to non-deterministic =

behaviour.

-- =

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@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Fri Jan 23 06:55:01 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BEB4F28C1B4; Fri, 23 Jan 2009 06:55:01 -0800 (PST)
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 E763628C1B4; Fri, 23 Jan 2009 06:55:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.847
X-Spam-Level: 
X-Spam-Status: No, score=-5.847 tagged_above=-999 required=5 tests=[AWL=0.752,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 8UqOUzmhwfpH; Fri, 23 Jan 2009 06:55:00 -0800 (PST)
Received: from smtp-bedford.mitre.org (smtp-bedford.mitre.org [129.83.20.191]) by core3.amsl.com (Postfix) with ESMTP id 6792C28C1B2; Fri, 23 Jan 2009 06:54:59 -0800 (PST)
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0NEsgQc026732;  Fri, 23 Jan 2009 09:54:42 -0500
Received: from imchub1.MITRE.ORG (imchub1.mitre.org [129.83.29.73]) by smtp-bedford.mitre.org (8.13.1/8.13.1) with ESMTP id n0NEsg2J026729;  Fri, 23 Jan 2009 09:54:42 -0500
Received: from IMCMBX1.MITRE.ORG ([129.83.29.204]) by imchub1.MITRE.ORG ([129.83.29.73]) with mapi; Fri, 23 Jan 2009 09:54:42 -0500
From: "Dunn, Jeffrey H." <jdunn@mitre.org>
To: Thomas Peterson <thomasp@iol.unh.edu>
Date: Fri, 23 Jan 2009 09:54:41 -0500
Subject: RE: End System PMTUD behavior question
Thread-Topic: End System PMTUD behavior question
Thread-Index: Acl80VYqdrLkaTMlRAetAiyxL5Cq/wAmQSxw
Message-ID: <3C6F21684E7C954193E6C7C4573B762701D3DD7322@IMCMBX1.MITRE.ORG>
References: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG> <200901212133.30109.rdenis@simphalempin.com> <3C6F21684E7C954193E6C7C4573B762701D3DD687B@IMCMBX1.MITRE.ORG> <42A4D5E1-C552-434C-90E3-DA3EF4A78688@iol.unh.edu> <3C6F21684E7C954193E6C7C4573B762701D3DD69D1@IMCMBX1.MITRE.ORG> <18F8D12C-DAA0-4F30-B405-9F54C15EACB4@iol.unh.edu>
In-Reply-To: <18F8D12C-DAA0-4F30-B405-9F54C15EACB4@iol.unh.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
Cc: "ipv6-bounces@ietf.org" <ipv6-bounces@ietf.org>, "Liou, Chern" <csliou@mitre.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "Sherman, Kurt T." <ksherman@mitre.org>, "steve_eiserman@uscourts.gov" <steve_eiserman@uscourts.gov>, "Huang, Frank" <fhuang@mitre.org>, "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, "Grayeli, Parisa" <pgrayeli@mitre.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/pipermail/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>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org Tom,

Many thanks for the information. Could you tell me the OS variants on the h=
osts and router? Also, do you have any tests involving applications?  I wil=
l send you an off-line e-mail to discuss possible additional testing.

Best Regards, =

=A0 =

Jeffrey Dunn =

Info Systems Eng., Lead =

MITRE Corporation.
(301) 448-6965 (mobile)


-----Original Message-----
From: Thomas Peterson [mailto:thomasp@iol.unh.edu] =

Sent: Thursday, January 22, 2009 3:38 PM
To: Dunn, Jeffrey H.
Cc: R=E9mi Denis-Courmont; ipv6@ietf.org; Huang, Frank; Sherman, Kurt T.; L=
iou, Chern; steve_eiserman@uscourts.gov; ipv6-bounces@ietf.org; v6ops@ops.i=
etf.org; Grayeli, Parisa
Subject: Re: End System PMTUD behavior question

Hi Jeffrey,

I have attached a picture which shows one of the topologies we use for  =

our PMTUD tests.

In this test case we transmit an Echo Request from REF-Host2 to TAR- =

Host1 with a packet size of 1500 bytes. REF-Host2 fragments the Echo  =

Request it transmits. TAR-Host1 replies to this Echo Request with an  =

Echo Reply to REF-Host2 with a size of 1500 bytes that is not  =

fragmented. TAR-Router1 sends a Packet Too Big message in response as  =

this Echo Reply is too large to forward onto Network 2.

In all of the cases we have seen TAR-Host1 does fragment future Echo  =

Replies to REF-Host2, however, it does not retransmit any Echo Replies  =

for Echo Requests received prior to receiving the Packet Too Big  =

message from TAR-Router1.

Additionally from the tests we have performed in our lab if TAR-Host1  =

were to send an Echo Request with a packet size of 1500 bytes TAR- =

Router1 would send a Packet Too Big message in response. In all cases  =

we have seen TAR-Host1 would not re-transmit this Echo Request and  =

this would be counted as packet loss in the ping command results.

If this does not ideally match your test scenario we'd be happy to  =

work together off-line to replicate your scenario.

Thanks,
Tom

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From ipv6-bounces@ietf.org  Fri Jan 23 08:51:15 2009
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 71B2B28C1E7; Fri, 23 Jan 2009 08:51:15 -0800 (PST)
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 D5AE628C1E7; Fri, 23 Jan 2009 08:51:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.341
X-Spam-Level: 
X-Spam-Status: No, score=-2.341 tagged_above=-999 required=5 tests=[AWL=0.258,  BAYES_00=-2.599]
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 qL-6pKC+vqwy; Fri, 23 Jan 2009 08:51:07 -0800 (PST)
Received: from postal.iol.unh.edu (postal.iol.unh.edu [132.177.123.84]) by core3.amsl.com (Postfix) with ESMTP id 3589A28C17F; Fri, 23 Jan 2009 08:51:07 -0800 (PST)
Received: from chinacat.iol.unh.edu (chinacat.iol.unh.edu [132.177.125.46]) by postal.iol.unh.edu (8.14.0/8.14.0) with ESMTP id n0NGoka8016920 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 23 Jan 2009 11:50:47 -0500
Message-Id: <AC2985F0-F72C-4AF4-B177-6DC29E0A943B@iol.unh.edu>
From: Thomas Peterson <thomasp@iol.unh.edu>
To: "Dunn, Jeffrey H." <jdunn@mitre.org>
In-Reply-To: <3C6F21684E7C954193E6C7C4573B762701D3DD7322@IMCMBX1.MITRE.ORG>
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: End System PMTUD behavior question
Date: Fri, 23 Jan 2009 11:50:47 -0500
References: <3C6F21684E7C954193E6C7C4573B762701D3DD67DA@IMCMBX1.MITRE.ORG> <200901212133.30109.rdenis@simphalempin.com> <3C6F21684E7C954193E6C7C4573B762701D3DD687B@IMCMBX1.MITRE.ORG> <42A4D5E1-C552-434C-90E3-DA3EF4A78688@iol.unh.edu> <3C6F21684E7C954193E6C7C4573B762701D3DD69D1@IMCMBX1.MITRE.ORG> <18F8D12C-DAA0-4F30-B405-9F54C15EACB4@iol.unh.edu> <3C6F21684E7C954193E6C7C4573B762701D3DD7322@IMCMBX1.MITRE.ORG>
X-Mailer: Apple Mail (2.930.3)
X-Virus-Scanned: ClamAV 0.94/8897/Fri Jan 23 07:59:36 2009 on postal.iol.unh.edu
X-Virus-Status: Clean
Cc: "ipv6-bounces@ietf.org" <ipv6-bounces@ietf.org>, "Liou, Chern" <csliou@mitre.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "Sherman, Kurt T." <ksherman@mitre.org>, "steve_eiserman@uscourts.gov" <steve_eiserman@uscourts.gov>, "Huang, Frank" <fhuang@mitre.org>, "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>, "Grayeli, Parisa" <pgrayeli@mitre.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/pipermail/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>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; DelSp="yes"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org Hi Jeffrey,

Here is a link to the list of all of the different hosts that we have  =

performed this testing on:

http://www.iol.unh.edu/services/testing/ipv6/equipment.php

Currently we use the ping application to test PTMUD, however, we would  =

be interested in performing addition tests  using various applications.

Thanks,
Tom

On Jan 23, 2009, at 9:54 AM, Dunn, Jeffrey H. wrote:

> Tom,
>
> Many thanks for the information. Could you tell me the OS variants  =

> on the hosts and router? Also, do you have any tests involving  =

> applications?  I will send you an off-line e-mail to discuss  =

> possible additional testing.
>
> Best Regards,
>
> Jeffrey Dunn
> Info Systems Eng., Lead
> MITRE Corporation.
> (301) 448-6965 (mobile)
>
>
> -----Original Message-----
> From: Thomas Peterson [mailto:thomasp@iol.unh.edu]
> Sent: Thursday, January 22, 2009 3:38 PM
> To: Dunn, Jeffrey H.
> Cc: R=E9mi Denis-Courmont; ipv6@ietf.org; Huang, Frank; Sherman, Kurt  =

> T.; Liou, Chern; steve_eiserman@uscourts.gov; ipv6-bounces@ietf.org; v6op=
s@ops.ietf.org =

> ; Grayeli, Parisa
> Subject: Re: End System PMTUD behavior question
>
> Hi Jeffrey,
>
> I have attached a picture which shows one of the topologies we use for
> our PMTUD tests.
>
> In this test case we transmit an Echo Request from REF-Host2 to TAR-
> Host1 with a packet size of 1500 bytes. REF-Host2 fragments the Echo
> Request it transmits. TAR-Host1 replies to this Echo Request with an
> Echo Reply to REF-Host2 with a size of 1500 bytes that is not
> fragmented. TAR-Router1 sends a Packet Too Big message in response as
> this Echo Reply is too large to forward onto Network 2.
>
> In all of the cases we have seen TAR-Host1 does fragment future Echo
> Replies to REF-Host2, however, it does not retransmit any Echo Replies
> for Echo Requests received prior to receiving the Packet Too Big
> message from TAR-Router1.
>
> Additionally from the tests we have performed in our lab if TAR-Host1
> were to send an Echo Request with a packet size of 1500 bytes TAR-
> Router1 would send a Packet Too Big message in response. In all cases
> we have seen TAR-Host1 would not re-transmit this Echo Request and
> this would be counted as packet loss in the ping command results.
>
> If this does not ideally match your test scenario we'd be happy to
> work together off-line to replicate your scenario.
>
> Thanks,
> Tom
>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
