From owner-v6ops@ops.ietf.org Thu Sep 01 06:48:17 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EAmcD-00064t-3K
	for v6ops-archive@megatron.ietf.org; Thu, 01 Sep 2005 06:48:17 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18986
	for <v6ops-archive@lists.ietf.org>; Thu, 1 Sep 2005 06:48:14 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EAmZd-000AZI-K0
	for v6ops-data@psg.com; Thu, 01 Sep 2005 10:45:37 +0000
Received: from [144.254.15.119] (helo=av-tac-bru.cisco.com)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EAmZb-000AZ3-GV
	for v6ops@ops.ietf.org; Thu, 01 Sep 2005 10:45:36 +0000
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id j81AjYH01147
	for <v6ops@ops.ietf.org>; Thu, 1 Sep 2005 12:45:34 +0200 (CEST)
Received: from gvandeve-w2k01.cisco.com (rtp-vpn1-33.cisco.com [10.82.224.33])
	by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id j81AjW302569
	for <v6ops@ops.ietf.org>; Thu, 1 Sep 2005 12:45:33 +0200 (CEST)
Message-Id: <4.3.2.7.2.20050901124115.04916658@strange-brew>
X-Sender: gvandeve@strange-brew
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 01 Sep 2005 12:45:29 +0200
To: v6ops@ops.ietf.org
From: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
Subject: Proposed Resolution of Issues [1-37]
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

The issue list available on http://www.vandevelde.cc/ietf/NAP-Issue-Log.htm has
been updated and addresses the remainder of the issues from the WGLC.

The Consensus answers in marked in blue are the onces that were proposed
last week and have been considered as stable consensus. The proposed resolution
entries marked in red are the onces added today.

Groetjes,
G/





From owner-v6ops@ops.ietf.org Thu Sep 01 07:15:26 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EAn2T-0007Tc-Uz
	for v6ops-archive@megatron.ietf.org; Thu, 01 Sep 2005 07:15:25 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27387
	for <v6ops-archive@lists.ietf.org>; Thu, 1 Sep 2005 07:15:23 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EAn0g-000H5W-Nd
	for v6ops-data@psg.com; Thu, 01 Sep 2005 11:13:34 +0000
Received: from [144.254.15.119] (helo=av-tac-bru.cisco.com)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EAn0W-000GvK-SB
	for v6ops@ops.ietf.org; Thu, 01 Sep 2005 11:13:25 +0000
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id j81BDN202907
	for <v6ops@ops.ietf.org>; Thu, 1 Sep 2005 13:13:23 +0200 (CEST)
Received: from gvandeve-w2k01.cisco.com (rtp-vpn1-33.cisco.com [10.82.224.33])
	by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id j81BDM325134
	for <v6ops@ops.ietf.org>; Thu, 1 Sep 2005 13:13:22 +0200 (CEST)
Message-Id: <4.3.2.7.2.20050901131205.04916ef8@strange-brew>
X-Sender: gvandeve@strange-brew
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 01 Sep 2005 13:13:19 +0200
To: v6ops@ops.ietf.org
From: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
Subject: [draft-ietf-v6ops-nap-01.txt] Proposed Resolution of Issues
  [1-37]
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

The issue list available on http://www.vandevelde.cc/ietf/NAP-Issue-Log.htm has
been updated and addresses the remainder of the issues from the WGLC.

The Consensus answers in marked in blue are the onces that were proposed
last week and have been considered as stable consensus. The proposed resolution
entries marked in red are the onces added today.

Groetjes,
G/ 





From owner-v6ops@ops.ietf.org Thu Sep 01 11:43:04 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EArDU-0008Qe-El
	for v6ops-archive@megatron.ietf.org; Thu, 01 Sep 2005 11:43:04 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11578
	for <v6ops-archive@lists.ietf.org>; Thu, 1 Sep 2005 11:43:02 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EArAT-000N5x-Mx
	for v6ops-data@psg.com; Thu, 01 Sep 2005 15:39:57 +0000
Received: from [152.78.70.1] (helo=raven.ecs.soton.ac.uk)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EArAQ-000N5Y-IT
	for v6ops@ops.ietf.org; Thu, 01 Sep 2005 15:39:54 +0000
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id j81FdrYO017678
	for <v6ops@ops.ietf.org>; Thu, 1 Sep 2005 16:39:53 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id QAA27929
	for <v6ops@ops.ietf.org>; Thu, 1 Sep 2005 16:39:44 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id j81FdiL02274
	for v6ops@ops.ietf.org; Thu, 1 Sep 2005 16:39:44 +0100
Date: Thu, 1 Sep 2005 16:39:44 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: v6ops@ops.ietf.org
Subject: Re: I-D ACTION:draft-huston-hd-metric-01.txt
Message-ID: <20050901153944.GB2098@login.ecs.soton.ac.uk>
Mail-Followup-To: v6ops@ops.ietf.org
References: <E1EAYav-0004Vw-I4@newodin.ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1EAYav-0004Vw-I4@newodin.ietf.org>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-MailScanner-From: tjc@smtp.ecs.soton.ac.uk
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

On Wed, Aug 31, 2005 at 03:50:01PM -0400, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 	Title		: Considerations on the IPv6 Host density Metric
> 	Author(s)	: G. Huston
> 	Filename	: draft-huston-hd-metric-01.txt
> 	Pages		: 18
> 	Date		: 2005-8-31
> 	
> This memo provides an analysis of the Host Density metric as
>    currently used to guide registry allocations of IPv6 unicast address
>    blocks.  This document contrasts the address efficiency as currently
>    adopted in the allocation of IPv4 network addresses and that used by
>    the IPv6 protocol.  It is noted that for large allocations there are
>    very significant variations in the target efficiency metric between
>    the two approaches.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-huston-hd-metric-01.txt

A couple of observations.

I note from RFC3194 that it says "The examples suggest an HD-ratio value
on the order of 85% and above correspond to a high pain level, at which
operators are ready to make drastic decisions" and that "...this suggests
that values of 80% or less corresponds to comfortable trade-offs between
pain and efficiency."

So the argument here is that very large networks don't share the same
HD ratio property?  I think it would be nice to state the crux of the 'case'
of this draft in the intro section.

I guess the references for 3513 and 3177 should point to the -bis versions
currently in draft?
        draft-ietf-ipv6-addr-arch-v4-04
        draft-narten-ipv6-3177bis-48boundary-00

This draft states assumptions about /48's, so should probably discuss the
impact of /56's being the default?   Or do you think Thomas' draft should
discuss this?   The two seem quite linked :)

-- 
Tim/::1






From owner-v6ops@ops.ietf.org Thu Sep 01 14:23:11 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EAtiQ-0001eE-QM
	for v6ops-archive@megatron.ietf.org; Thu, 01 Sep 2005 14:23:11 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18601
	for <v6ops-archive@lists.ietf.org>; Thu, 1 Sep 2005 14:23:07 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EAtgX-0007nV-I9
	for v6ops-data@psg.com; Thu, 01 Sep 2005 18:21:13 +0000
Received: from [171.71.176.71] (helo=sj-iport-2.cisco.com)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EAtgV-0007nH-Pf
	for v6ops@ops.ietf.org; Thu, 01 Sep 2005 18:21:11 +0000
Received: from sj-core-1.cisco.com ([171.71.177.237])
  by sj-iport-2.cisco.com with ESMTP; 01 Sep 2005 11:21:12 -0700
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j81IL60J024240;
	Thu, 1 Sep 2005 11:21:06 -0700 (PDT)
Received: from [10.32.244.220] (stealth-10-32-244-220.cisco.com [10.32.244.220])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id j81IGgre020933;
	Thu, 1 Sep 2005 11:16:42 -0700
In-Reply-To: <20050901153944.GB2098@login.ecs.soton.ac.uk>
References: <E1EAYav-0004Vw-I4@newodin.ietf.org> <20050901153944.GB2098@login.ecs.soton.ac.uk>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5BC75BE1-F807-4AEF-AD63-EBCE0A0F4024@cisco.com>
Cc: v6ops@ops.ietf.org
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: I-D ACTION:draft-huston-hd-metric-01.txt
Date: Thu, 1 Sep 2005 11:21:05 -0700
To: Tim Chown <tjc@ecs.soton.ac.uk>, Geoff Huston <gih@apnic.net>,
        Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.734)
DKIM-Signature: a=rsa-sha1;  q=dns; l=1815; t=1125598603; x=1126030803;
	c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding;
	d=cisco.com; i=fred@cisco.com; 
	z=Subject:Re=3A=20I-D=20ACTION=3Adraft-huston-hd-metric-01.txt|
	From:Fred=20Baker=20<fred@cisco.com>|
	Date:Thu,=201=20Sep=202005=2011=3A21=3A05=20-0700|
	Content-Type:text/plain=3B=20charset=3DUS-ASCII=3B=20delsp=3Dyes=3B=20format=3Dflowed|
	Content-Transfer-Encoding:7bit;
	b=RggSk4T3eNrGQYBaOWgh+QrxkQKpqdEitRSEpAZD1aCrgGvrzz6P8ZCEdhn+PSEbPn3kQwCC
	xDCvrXtff4hPIL9GAW07QftkirZcofrB5yYSiam+VUsDaCeL0brlhdVqkVbX4/F4df5VS+21Bh+
	XM8G1aAtI1xFt2BPvfTr+Qt8=
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com; dkim=pass (
	message from cisco.com verified; ); 
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Are you of the opinion that we should take this, and perhaps Thomas'  
draft, up as a v6ops draft?

(I would question whether free advice on address allocation policy is  
actually an IPv6 WG topic as much as an operational topic anyway, and  
certainly comments on the HD ratio is an operational topic)

On Sep 1, 2005, at 8:39 AM, Tim Chown wrote:
> On Wed, Aug 31, 2005 at 03:50:01PM -0400, Internet-Drafts@ietf.org  
> wrote:
>
>> A New Internet-Draft is available from the on-line Internet-Drafts  
>> directories.
>>     Title        : Considerations on the IPv6 Host density Metric
>>     Author(s)    : G. Huston
>>     Filename    : draft-huston-hd-metric-01.txt
>>     Pages        : 18
>>     Date        : 2005-8-31
>>
>> This memo provides an analysis of the Host Density metric as
>>    currently used to guide registry allocations of IPv6 unicast  
>> address
>>    blocks.  This document contrasts the address efficiency as  
>> currently
>>    adopted in the allocation of IPv4 network addresses and that  
>> used by
>>    the IPv6 protocol.  It is noted that for large allocations  
>> there are
>>    very significant variations in the target efficiency metric  
>> between
>>    the two approaches.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-huston-hd-metric-01.txt
>>
>
> A couple of observations.
>
> I note from RFC3194 that it says "The examples suggest an HD-ratio  
> value
> on the order of 85% and above correspond to a high pain level, at  
> which
> operators are ready to make drastic decisions" and that "...this  
> suggests
> that values of 80% or less corresponds to comfortable trade-offs  
> between
> pain and efficiency."
>
> So the argument here is that very large networks don't share the same
> HD ratio property?  I think it would be nice to state the crux of  
> the 'case'
> of this draft in the intro section.
>
> I guess the references for 3513 and 3177 should point to the -bis  
> versions
> currently in draft?
>         draft-ietf-ipv6-addr-arch-v4-04
>         draft-narten-ipv6-3177bis-48boundary-00
>
> This draft states assumptions about /48's, so should probably  
> discuss the
> impact of /56's being the default?   Or do you think Thomas' draft  
> should
> discuss this?   The two seem quite linked :)
>
> -- 
> Tim/::1
>
>




From owner-v6ops@ops.ietf.org Fri Sep 02 04:13:41 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EB6g7-0003dq-IE
	for v6ops-archive@megatron.ietf.org; Fri, 02 Sep 2005 04:13:41 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22014
	for <v6ops-archive@lists.ietf.org>; Fri, 2 Sep 2005 04:13:37 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EB6ca-000PWo-U4
	for v6ops-data@psg.com; Fri, 02 Sep 2005 08:10:00 +0000
Received: from [152.78.70.1] (helo=raven.ecs.soton.ac.uk)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EB6cY-000PVX-Ru
	for v6ops@ops.ietf.org; Fri, 02 Sep 2005 08:09:59 +0000
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id j82898YO006635;
	Fri, 2 Sep 2005 09:09:08 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id JAA16166;
	Fri, 2 Sep 2005 09:08:49 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id j8288mM18621;
	Fri, 2 Sep 2005 09:08:48 +0100
Date: Fri, 2 Sep 2005 09:08:48 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: Fred Baker <fred@cisco.com>
Cc: Geoff Huston <gih@apnic.net>, Thomas Narten <narten@us.ibm.com>,
        v6ops@ops.ietf.org
Subject: Re: I-D ACTION:draft-huston-hd-metric-01.txt
Message-ID: <20050902080848.GJ17558@login.ecs.soton.ac.uk>
Mail-Followup-To: Fred Baker <fred@cisco.com>, Geoff Huston <gih@apnic.net>,
	Thomas Narten <narten@us.ibm.com>, v6ops@ops.ietf.org
References: <E1EAYav-0004Vw-I4@newodin.ietf.org> <20050901153944.GB2098@login.ecs.soton.ac.uk> <5BC75BE1-F807-4AEF-AD63-EBCE0A0F4024@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5BC75BE1-F807-4AEF-AD63-EBCE0A0F4024@cisco.com>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-MailScanner-From: tjc@smtp.ecs.soton.ac.uk
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

Hi Fred,

These sem to be very operational issues to me.  I think both are views
of the same overall issue, i.e. evolving the 'big picture' for BCP in
IPv6 address allocation and management.   Thomas cites the HD ratio
in his draft, for example, but not Geoff's draft (I think!).

I think an interesting bit of RFC3177 is the reasoning for a fixed /48
boundary in section 3.  Issues like multihoming and site-locals that
are discussed, but I don't think Thomas picks those up.  3177 talks of 
leaving the option to retrofit an 8+8 multihoming model, but I think 
we're now heading a different way with shim6.  3177 also talks about 
site locals, which would lead to the implication that we'll need to
modify ULAs to be /56 friendly if Thomas' suggestions are adopted.

Tim

On Thu, Sep 01, 2005 at 11:21:05AM -0700, Fred Baker wrote:
> Are you of the opinion that we should take this, and perhaps Thomas'  
> draft, up as a v6ops draft?
> 
> (I would question whether free advice on address allocation policy is  
> actually an IPv6 WG topic as much as an operational topic anyway, and  
> certainly comments on the HD ratio is an operational topic)
> 
> On Sep 1, 2005, at 8:39 AM, Tim Chown wrote:
> >On Wed, Aug 31, 2005 at 03:50:01PM -0400, Internet-Drafts@ietf.org  
> >wrote:
> >
> >>A New Internet-Draft is available from the on-line Internet-Drafts  
> >>directories.
> >>    Title        : Considerations on the IPv6 Host density Metric
> >>    Author(s)    : G. Huston
> >>    Filename    : draft-huston-hd-metric-01.txt
> >>    Pages        : 18
> >>    Date        : 2005-8-31
> >>
> >>This memo provides an analysis of the Host Density metric as
> >>   currently used to guide registry allocations of IPv6 unicast  
> >>address
> >>   blocks.  This document contrasts the address efficiency as  
> >>currently
> >>   adopted in the allocation of IPv4 network addresses and that  
> >>used by
> >>   the IPv6 protocol.  It is noted that for large allocations  
> >>there are
> >>   very significant variations in the target efficiency metric  
> >>between
> >>   the two approaches.
> >>
> >>A URL for this Internet-Draft is:
> >>http://www.ietf.org/internet-drafts/draft-huston-hd-metric-01.txt
> >>
> >
> >A couple of observations.
> >
> >I note from RFC3194 that it says "The examples suggest an HD-ratio  
> >value
> >on the order of 85% and above correspond to a high pain level, at  
> >which
> >operators are ready to make drastic decisions" and that "...this  
> >suggests
> >that values of 80% or less corresponds to comfortable trade-offs  
> >between
> >pain and efficiency."
> >
> >So the argument here is that very large networks don't share the same
> >HD ratio property?  I think it would be nice to state the crux of  
> >the 'case'
> >of this draft in the intro section.
> >
> >I guess the references for 3513 and 3177 should point to the -bis  
> >versions
> >currently in draft?
> >        draft-ietf-ipv6-addr-arch-v4-04
> >        draft-narten-ipv6-3177bis-48boundary-00
> >
> >This draft states assumptions about /48's, so should probably  
> >discuss the
> >impact of /56's being the default?   Or do you think Thomas' draft  
> >should
> >discuss this?   The two seem quite linked :)
> >
> >-- 
> >Tim/::1
> >
> >

-- 
Tim/::1






From owner-v6ops@ops.ietf.org Fri Sep 02 04:33:50 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EB6ze-0004xt-BG
	for v6ops-archive@megatron.ietf.org; Fri, 02 Sep 2005 04:33:50 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23396
	for <v6ops-archive@lists.ietf.org>; Fri, 2 Sep 2005 04:33:48 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EB6z2-00053A-6U
	for v6ops-data@psg.com; Fri, 02 Sep 2005 08:33:12 +0000
Received: from [152.78.70.1] (helo=raven.ecs.soton.ac.uk)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EB6z0-00052k-6P
	for v6ops@ops.ietf.org; Fri, 02 Sep 2005 08:33:10 +0000
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id j828X8YO007052
	for <v6ops@ops.ietf.org>; Fri, 2 Sep 2005 09:33:09 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id JAA17795
	for <v6ops@ops.ietf.org>; Fri, 2 Sep 2005 09:33:00 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id j828X0619128
	for v6ops@ops.ietf.org; Fri, 2 Sep 2005 09:33:00 +0100
Date: Fri, 2 Sep 2005 09:33:00 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: v6ops@ops.ietf.org
Subject: Re: Proposed Resolution of Issues [1-37]
Message-ID: <20050902083300.GL17558@login.ecs.soton.ac.uk>
Mail-Followup-To: v6ops@ops.ietf.org
References: <4.3.2.7.2.20050901124115.04916658@strange-brew>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.3.2.7.2.20050901124115.04916658@strange-brew>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-MailScanner-From: tjc@smtp.ecs.soton.ac.uk
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

On Thu, Sep 01, 2005 at 12:45:29PM +0200, Gunter Van de Velde (gvandeve) wrote:
> The issue list available on http://www.vandevelde.cc/ietf/NAP-Issue-Log.htm 
> has
> been updated and addresses the remainder of the issues from the WGLC.
> 
> The Consensus answers in marked in blue are the onces that were proposed
> last week and have been considered as stable consensus. The proposed 
> resolution
> entries marked in red are the onces added today.

Looks good.

For issue 5, RFC3041 might hamper that.

On Issue 9, I suspect Kurtis has good figures on this, I recall he did 
back before multi6 reformed and we had multihoming discussions in Michel's
list.  

Issue 10, because admins pick 10.0.0.0/24 or 192.168.0.0/24.  I'll wager
they do the same with ULAs still, but hey :)

Issue 12 ULAs dont aggregate internally either, as each /48 is in effect
a random prefix.  May bug big organisations, who thus may not use 'proper'
ULAs?

Issue 14 - as Stig pointed out, if two remote sites use ULAs they may
prfer to use ULAs between them.   But that could be configured as 3484
policy too.   The key thing is that ULAs now have global scope, so are
by default treated as globals.

Issue 20 - I'm very wary that we should not embed 'best practice' in
firewall configuration in this draft.  I'd say 'less is more' here.

Issue 23 - unique but may change, eg. 3041.  I see little difference from
the ISP view in a customer with a stable single v4 address + NAT and a
customer with a stable /56 prefix and 3041 in use.  The v4 address masks
systems just as the /56 in effect does.

Issue 24 - so what text will you use? :)

Issue 27... hmmmm.  Renumbering complexity has many variables.  A simple
home network with one LAN and no servers/services is as easy as it gets.
I'd assume that most current NAT-using sites don't have many externally
advertised services, but will embed IP addresses in their internal systems
and networks.

Issues 32&33:  ULAs *may* help renumbering, not *will*.  There is baggage 
with ULAs and as such their use is a tradeoff not a given, I feel.

Issue 36: in practice sites will run IPv6 with IPv4+NAT, so they need
to secure two protocols 'on the wire'.

Issue 37: noone is mandating a migration from IPv4+NAT to IPv6.  Indeed
many sites may equally benefit from a migration to use global IPv4 addresses.
One might even consider in the draft how much is IPv6 specific, and how
much is 'use global addresses' specific.

I'll also resubmit the posrt-scanning text soon.

-- 
Tim/::1






From owner-v6ops@ops.ietf.org Fri Sep 02 17:20:07 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EBIxD-00023T-D5
	for v6ops-archive@megatron.ietf.org; Fri, 02 Sep 2005 17:20:07 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03330
	for <v6ops-archive@lists.ietf.org>; Fri, 2 Sep 2005 17:20:05 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EBIvG-000NyL-SG
	for v6ops-data@psg.com; Fri, 02 Sep 2005 21:18:06 +0000
Received: from [171.71.176.70] (helo=sj-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EBIvG-000Ny7-51
	for v6ops@ops.ietf.org; Fri, 02 Sep 2005 21:18:06 +0000
Received: from sj-core-1.cisco.com ([171.71.177.237])
  by sj-iport-1.cisco.com with ESMTP; 02 Sep 2005 14:18:06 -0700
X-IronPort-AV: i="3.96,165,1122879600"; 
   d="scan'208"; a="658148685:sNHT35238572"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j82LI00J028325;
	Fri, 2 Sep 2005 14:18:00 -0700 (PDT)
Received: from [10.32.244.220] (stealth-10-32-244-220.cisco.com [10.32.244.220])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id j82LDXSR001994;
	Fri, 2 Sep 2005 14:13:33 -0700
In-Reply-To: <20050902083300.GL17558@login.ecs.soton.ac.uk>
References: <4.3.2.7.2.20050901124115.04916658@strange-brew> <20050902083300.GL17558@login.ecs.soton.ac.uk>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9B968269-D9E5-4F6C-8F17-B5931D8879DE@cisco.com>
Cc: v6ops@ops.ietf.org
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: Proposed Resolution of Issues [1-37]
Date: Fri, 2 Sep 2005 14:18:00 -0700
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.734)
DKIM-Signature: a=rsa-sha1;  q=dns; l=2163; t=1125695613; x=1126127813;
	c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding;
	d=cisco.com; i=fred@cisco.com; 
	z=Subject:Re=3A=20Proposed=20Resolution=20of=20Issues=20[1-37]|
	From:Fred=20Baker=20<fred@cisco.com>|
	Date:Fri,=202=20Sep=202005=2014=3A18=3A00=20-0700|
	Content-Type:text/plain=3B=20charset=3DUS-ASCII=3B=20delsp=3Dyes=3B=20format=3Dflowed|
	Content-Transfer-Encoding:7bit;
	b=VzBvGfHpAlJDv3KG98KtyRFUAerBSXpppJnnAPsAkZYPDX1sAiLj45ezJEgaLg8/gnJEXJJ/
	rvUErICSAdZE3DSivmK8GYIB6mX9eP8rM7D0nzOdekZvG7j2Hszb81488AjGhW7QG69Irzr2y8e
	n16WaqhzgmeAaaJPgDPXI14M=
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com; dkim=pass (
	message from cisco.com verified; ); 
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

On Sep 2, 2005, at 1:33 AM, Tim Chown wrote:
> Issues 32&33:  ULAs *may* help renumbering, not *will*.  There is  
> baggage
> with ULAs and as such their use is a tradeoff not a given, I feel.

I very much agree. I had the same debate with Pekka and Thomas when  
the renumbering procedure draft went in. Thomas filed a 'discuss'  
requiring me to say that ULAs would simplify renumbering, but without  
saying how. I told them:

On Jan 15, 2005, at 5:46 PM, Fred Baker wrote:
> Listen. If ULAs simplify the procedure of renumbering a network  
> without a flag day, then there should be several places in the  
> document where a few sentences of the following form can be added.
>
>   "if the old prefix..." or "if the new prefix..."
>   "is a ULA prefix then"
>   "...this step may be skipped" or "...this step may be simplified  
> <in this way>"
>   "and it still allows you to renumber a network without a flag day  
> for <this> reason."
>
> Present me with those sentences, and I will include them.

On Jan 15, 2005, at 9:34 AM, Fred Baker wrote:
>> This said, I think it's still good idea to _mention_ ULAs, but  
>> treat them with sufficient skepticism at this point.  The text you  
>> proposed, and which I modified, and suggested in the previous  
>> message:
>>
>>> This document describes issues related to renumbering a network,  
>>> where network addresses need to be changed because the old  
>>> numbers will no longer be usable in the future. Readers should be  
>>> aware that a form of local addressing, Unique Local Addressing  
>>> (ULA) [ULA].  Using ULA addresses doesn't obviate the need to  
>>> renumber networks, but are another tool that may reduce the need  
>>> for or complexity of renumbering networks.
>
> This document, first and foremost, is about a procedure for  
> renumbering a network. Both you and Thomas suggest that ULAs might  
> reduce the complexity involved in numbering networks, but I am at a  
> loss to say how - and in the end, when people ask that question,  
> they will ask it of the authors. In neither the text you propose  
> nor the text Thomas proposes do I see any suggestion of a way that  
> ULAs might alter that procedure in any way. Am I missing something?
>
> If you can't tell me *how* ULAs reduce the complexity in the  
> procedure of renumbering a network, I don't see the mention as  
> relevant.

I have heard a fair bit of dogma about ULAs to the effect that they  
solve something, but have never been presented with those sentences,  
and am not convinced on the rest either. They look to me like a re- 
invention of site-local with many of the same problems.

And by the way, if ULAs are global, they are global addresses... What  
does the "L" stand for?







From owner-v6ops@ops.ietf.org Sun Sep 04 04:19:01 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EBpiP-00056v-Im
	for v6ops-archive@megatron.ietf.org; Sun, 04 Sep 2005 04:19:01 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27514
	for <v6ops-archive@lists.ietf.org>; Sun, 4 Sep 2005 04:18:59 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EBpf7-000Dc1-Hj
	for v6ops-data@psg.com; Sun, 04 Sep 2005 08:15:37 +0000
Received: from [152.78.70.1] (helo=raven.ecs.soton.ac.uk)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EBpf5-000Dbj-Ic
	for v6ops@ops.ietf.org; Sun, 04 Sep 2005 08:15:35 +0000
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id j848FXiN010300
	for <v6ops@ops.ietf.org>; Sun, 4 Sep 2005 09:15:34 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id JAA10698
	for <v6ops@ops.ietf.org>; Sun, 4 Sep 2005 09:15:24 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id j848FOD21884
	for v6ops@ops.ietf.org; Sun, 4 Sep 2005 09:15:24 +0100
Date: Sun, 4 Sep 2005 09:15:24 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: v6ops@ops.ietf.org
Subject: Re: Proposed Resolution of Issues [1-37]
Message-ID: <20050904081524.GD21793@login.ecs.soton.ac.uk>
Mail-Followup-To: v6ops@ops.ietf.org
References: <4.3.2.7.2.20050901124115.04916658@strange-brew> <20050902083300.GL17558@login.ecs.soton.ac.uk> <9B968269-D9E5-4F6C-8F17-B5931D8879DE@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9B968269-D9E5-4F6C-8F17-B5931D8879DE@cisco.com>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-MailScanner-From: tjc@smtp.ecs.soton.ac.uk
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

On Fri, Sep 02, 2005 at 02:18:00PM -0700, Fred Baker wrote:
> 
> And by the way, if ULAs are global, they are global addresses... What  
> does the "L" stand for?

I've been wondering that too ;)

-- 
Tim/::1






From owner-v6ops@ops.ietf.org Mon Sep 05 05:18:36 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ECD7Z-0004Qr-Bc
	for v6ops-archive@megatron.ietf.org; Mon, 05 Sep 2005 05:18:36 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05853
	for <v6ops-archive@lists.ietf.org>; Mon, 5 Sep 2005 05:18:30 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1ECD1Y-000Aow-AJ
	for v6ops-data@psg.com; Mon, 05 Sep 2005 09:12:20 +0000
Received: from [193.252.22.31] (helo=smtp11.wanadoo.fr)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1ECD1W-000Aog-2z
	for v6ops@ops.ietf.org; Mon, 05 Sep 2005 09:12:18 +0000
Received: from me-wanadoo.net (localhost [127.0.0.1])
	by mwinf1106.wanadoo.fr (SMTP Server) with ESMTP id CF0E11C000B5
	for <v6ops@ops.ietf.org>; Mon,  5 Sep 2005 11:12:16 +0200 (CEST)
Received: from [192.168.1.100] (APuteaux-153-1-27-22.w82-124.abo.wanadoo.fr [82.124.189.22])
	by mwinf1106.wanadoo.fr (SMTP Server) with ESMTP id 292C21C0009B;
	Mon,  5 Sep 2005 11:12:15 +0200 (CEST)
X-ME-UUID: 20050905091216168.292C21C0009B@mwinf1106.wanadoo.fr
Message-ID: <431C0BEE.1050701@rd-iptech.com>
Date: Mon, 05 Sep 2005 11:12:14 +0200
From: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@rd-iptech.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>
Subject: Re: RV: I-D ACTION:draft-baker-v6ops-end2end-00.txt
References: <BF26D502.120C60%jordi.palet@consulintel.es> <456CB87D-36EE-4282-B390-5E73C9C5F66D@cisco.com> <4302E5A1.9090803@rd-iptech.com> <Pine.LNX.4.61.0508181255450.1622@netcore.fi> <430484F8.20206@rd-iptech.com> <20050819091509.GT30371@login.ecs.soton.ac.uk>
In-Reply-To: <20050819091509.GT30371@login.ecs.soton.ac.uk>
Content-Type: multipart/alternative;
 boundary="------------070201040003010809000303"
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,HTML_30_40,
	HTML_MESSAGE,HTML_TITLE_EMPTY autolearn=no version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.
--------------070201040003010809000303
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA05853

Tim Chown wrote:

>On Thu, Aug 18, 2005 at 02:54:16PM +0200, R=E9mi Despr=E9s wrote:
> =20
>
>>   Please don't hesitate to ask for more clarifications.
>>   I am aware they are needed, and it helps making progress.
>>   =20
>>
>
>The stumbling block to me digging deeply into your work is the terminolo=
gy
>used.  It's not using conventional language and terms.
>
I was trying to use new terminology only where it seemed useful.
But for the next step I will try to do better.
(In the mean time, if you could sindicate a few terms in particular I=20
should replace, that would be helpful.)

Thanks,
R=E9mi
+33 6 72 74 94 88

PS: this answer comes late because I happen to have been on vacation not=20
far from your university.
With my wife, we visited southern England, in particular Winchester,=20
Salisbury, Sonehenge, Stourhead Garden, Wilton House etc.
It was a very pleasant experience :-).

--------------070201040003010809000303
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Tim Chown wrote:
<blockquote cite="mid20050819091509.GT30371@login.ecs.soton.ac.uk"
 type="cite">
  <pre wrap="">On Thu, Aug 18, 2005 at 02:54:16PM +0200, R&eacute;mi Despr&eacute;s wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">   Please don't hesitate to ask for more clarifications.
   I am aware they are needed, and it helps making progress.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
The stumbling block to me digging deeply into your work is the terminology
used.  It's not using conventional language and terms.</pre>
</blockquote>
I was trying to use new terminology only where it seemed useful.<br>
But for the next step I will try to do better.<br>
(In the mean time, if you could sindicate a few terms in particular I
should replace, that would be helpful.)<br>
<br>
Thanks,<br>
R&eacute;mi<br>
+33 6 72 74 94 88<br>
<br>
PS: this answer comes late because I happen to have been on vacation
not far from your university.<br>
With my wife, we visited southern England, in particular Winchester,
Salisbury, Sonehenge, Stourhead Garden, Wilton House etc.<br>
It was a very pleasant experience :-).<br>
</body>
</html>

--------------070201040003010809000303--





From owner-v6ops@ops.ietf.org Tue Sep 06 10:39:04 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ECebF-0003IV-Ei
	for v6ops-archive@megatron.ietf.org; Tue, 06 Sep 2005 10:39:04 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01360
	for <v6ops-archive@lists.ietf.org>; Tue, 6 Sep 2005 10:38:59 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1ECeWU-0002HU-3G
	for v6ops-data@psg.com; Tue, 06 Sep 2005 14:34:06 +0000
Received: from [32.97.182.144] (helo=e4.ny.us.ibm.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.50 (FreeBSD))
	id 1ECeWS-0002HE-5f
	for v6ops@ops.ietf.org; Tue, 06 Sep 2005 14:34:04 +0000
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11])
	by e4.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id j86EY2Ll002742
	for <v6ops@ops.ietf.org>; Tue, 6 Sep 2005 10:34:02 -0400
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169])
	by westrelay02.boulder.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j86EWfMC516700
	for <v6ops@ops.ietf.org>; Tue, 6 Sep 2005 08:32:42 -0600
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1])
	by d03av03.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id j86EWfE2006707
	for <v6ops@ops.ietf.org>; Tue, 6 Sep 2005 08:32:41 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-49-155-50.mts.ibm.com [9.49.155.50])
	by d03av03.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j86EWeMr006682;
	Tue, 6 Sep 2005 08:32:41 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.13.1/8.12.5) with ESMTP id j86EWXUL004607;
	Tue, 6 Sep 2005 10:32:34 -0400
Message-Id: <200509061432.j86EWXUL004607@cichlid.raleigh.ibm.com>
To: Fred Baker <fred@cisco.com>
cc: Tim Chown <tjc@ecs.soton.ac.uk>, Geoff Huston <gih@apnic.net>,
        v6ops@ops.ietf.org
Subject: Re: I-D ACTION:draft-huston-hd-metric-01.txt 
In-Reply-To: Message from Fred Baker <fred@cisco.com> 
   of "Thu, 01 Sep 2005 11:21:05 PDT." <5BC75BE1-F807-4AEF-AD63-EBCE0A0F4024@cisco.com> 
Date: Tue, 06 Sep 2005 10:32:33 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

> Are you of the opinion that we should take this, and perhaps Thomas'  
> draft, up as a v6ops draft?

FWIW, I think the 3177bis document is more appropriate as an IPv6 WG
document than a v6ops one. In particular, a major goal of the document
is to document what _technical_ and _architectural_ relate to a
boundary of /56 vs. /48. (And it is my expectation that the answer is
that there are none).

That doesn't mean that v6ops shouldn't review and provide input; I
encourage them to do so.

If there are _operational_ issues of having end sites obtain a /56
rather than a /48, that would be good to hear about. I suppose there
could be some, but again I can't think right off of any major ones.

> (I would question whether free advice on address allocation policy is  
> actually an IPv6 WG topic as much as an operational topic anyway, and  
> certainly comments on the HD ratio is an operational topic)

Right. Comments on HD ratio might well be more appropriate for v6ops
than IPv6. But I'm not sure right off that Geoff's document should be
a v6ops WG document. It clearly needs review from multiple parties,
including v6ops & (say) the IAB. But ultimately its likely target is
informational, rather than BCP. Also,  its _real_ target/consituancy
is the RIR community. And operational issues about address policy are
expected to be discussed there already. 

Thomas




From owner-v6ops@ops.ietf.org Tue Sep 06 12:01:24 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ECfsy-0008JE-CS
	for v6ops-archive@megatron.ietf.org; Tue, 06 Sep 2005 12:01:24 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05175
	for <v6ops-archive@lists.ietf.org>; Tue, 6 Sep 2005 12:01:21 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1ECfpb-0008es-Vj
	for v6ops-data@psg.com; Tue, 06 Sep 2005 15:57:55 +0000
Received: from [204.127.198.39] (helo=rwcrmhc12.comcast.net)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1ECfpa-0008eT-7u
	for v6ops@ops.ietf.org; Tue, 06 Sep 2005 15:57:54 +0000
Received: from s73602 (unknown[65.104.224.98])
          by comcast.net (rwcrmhc13) with SMTP
          id <2005090615444001500i81qje>; Tue, 6 Sep 2005 15:44:40 +0000
Message-ID: <034701c5b2f9$e7472f10$0500a8c0@china.huawei.com>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <v6ops@ops.ietf.org>
References: <200509061432.j86EWXUL004607@cichlid.raleigh.ibm.com>
Subject: Re: I-D ACTION:draft-huston-hd-metric-01.txt 
Date: Tue, 6 Sep 2005 10:44:43 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

From: "Thomas Narten" <narten@us.ibm.com>
To: "Fred Baker" <fred@cisco.com>


>> Are you of the opinion that we should take this, and perhaps Thomas'
>> draft, up as a v6ops draft?
>
> FWIW, I think the 3177bis document is more appropriate as an IPv6 WG
> document than a v6ops one.

From the Paris meeting minutes at 
http://www3.ietf.org/proceedings/05aug/minutes/ipv6.txt

10. Next Steps for IPv6 w.g.     (Hinden)
    Advancing core specification to Standard
    Goal: Discussion

    Since 1994 we have published 61 RFCs!  Core protocols went to
    Draft Standard in 1998.  Working group scheduled to close end of
    this year.

Is IPv6 still taking on new work? (Not saying it shouldn't - actually, I 
have another draft that is also targeting IPv6 - but I thought I should 
ask).

Thanks,

Spencer





From owner-v6ops@ops.ietf.org Wed Sep 07 09:53:40 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ED0Ms-0005zA-39
	for v6ops-archive@megatron.ietf.org; Wed, 07 Sep 2005 09:53:40 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20430
	for <v6ops-archive@lists.ietf.org>; Wed, 7 Sep 2005 09:53:34 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1ED0ID-000Pmi-Vp
	for v6ops-data@psg.com; Wed, 07 Sep 2005 13:48:49 +0000
Received: from [195.212.29.150] (helo=mtagate1.de.ibm.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.50 (FreeBSD))
	id 1ED0IC-000PmL-GC
	for v6ops@ops.ietf.org; Wed, 07 Sep 2005 13:48:48 +0000
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49])
	by mtagate1.de.ibm.com (8.12.10/8.12.10) with ESMTP id j87DmHOI150426
	for <v6ops@ops.ietf.org>; Wed, 7 Sep 2005 13:48:18 GMT
Received: from d12av01.megacenter.de.ibm.com (d12av01.megacenter.de.ibm.com [9.149.165.212])
	by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j87DmHxv140894
	for <v6ops@ops.ietf.org>; Wed, 7 Sep 2005 15:48:17 +0200
Received: from d12av01.megacenter.de.ibm.com (loopback [127.0.0.1])
	by d12av01.megacenter.de.ibm.com (8.12.11/8.13.3) with ESMTP id j87DmGUf013658
	for <v6ops@ops.ietf.org>; Wed, 7 Sep 2005 15:48:17 +0200
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d12av01.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id j87DmGIx013625;
	Wed, 7 Sep 2005 15:48:16 +0200
Received: from zurich.ibm.com (sig-9-145-249-185.de.ibm.com [9.145.249.185])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id PAA11448;
	Wed, 7 Sep 2005 15:48:14 +0200
Message-ID: <431EEF9B.6090806@zurich.ibm.com>
Date: Wed, 07 Sep 2005 15:48:11 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
CC: Tim Chown <tjc@ecs.soton.ac.uk>, v6ops@ops.ietf.org
Subject: Re: Proposed Resolution of Issues [1-37]
References: <4.3.2.7.2.20050901124115.04916658@strange-brew> <20050902083300.GL17558@login.ecs.soton.ac.uk> <9B968269-D9E5-4F6C-8F17-B5931D8879DE@cisco.com>
In-Reply-To: <9B968269-D9E5-4F6C-8F17-B5931D8879DE@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Fred Baker wrote:
> On Sep 2, 2005, at 1:33 AM, Tim Chown wrote:
> 
>> Issues 32&33:  ULAs *may* help renumbering, not *will*.  There is  
>> baggage
>> with ULAs and as such their use is a tradeoff not a given, I feel.
> 
> 
> I very much agree. I had the same debate with Pekka and Thomas when  the 
> renumbering procedure draft went in. Thomas filed a 'discuss'  requiring 
> me to say that ULAs would simplify renumbering, but without  saying how. 
> I told them:
> 
> On Jan 15, 2005, at 5:46 PM, Fred Baker wrote:
> 
>> Listen. If ULAs simplify the procedure of renumbering a network  
>> without a flag day, then there should be several places in the  
>> document where a few sentences of the following form can be added.
>>
>>   "if the old prefix..." or "if the new prefix..."
>>   "is a ULA prefix then"
>>   "...this step may be skipped" or "...this step may be simplified  
>> <in this way>"
>>   "and it still allows you to renumber a network without a flag day  
>> for <this> reason."
>>
>> Present me with those sentences, and I will include them.

I don't think any of that applies. My take is that ULAs have the advantage
during a renumbering exercise of providing business continuity for
*internal* operations - your printers, for example, can have ULAs
and are untouched (and their DNS entries are untouched) during the
renumbering process. Your internal SMTP system can keep
operating without any change to internal DNS. Etc. So it does take
a number of hosts off the renumbering list - exactly those
hosts that have no external visibility.

<snip>

>> If you can't tell me *how* ULAs reduce the complexity in the  
>> procedure of renumbering a network, I don't see the mention as  relevant.
> 
> 
> I have heard a fair bit of dogma about ULAs to the effect that they  
> solve something, but have never been presented with those sentences,  
> and am not convinced on the rest either. They look to me like a re- 
> invention of site-local with many of the same problems.

No. They don't have the problem of ambiguity. In context of massive
hosting centers for hundreds of customers, they are vastly better
than RFC 1918 addresses (which is the comparison my operational
colleagues make).

But you do have to accept that a large number of enterprise
networks *want* private address space precisely because it isn't
supposed to be globally routeable. That may not be intellectually
satisfactory as a reason, but it seems to be reality.

> And by the way, if ULAs are global, they are global addresses... What  
> does the "L" stand for?

They're not global. They're globally unique but intended for local use.
However, "local" can mean a whole enterprise intranet plus VPNs to its
business partners. In that context, global uniqueness is a desirable
property.

     Brian






From Panek@xrs.net Mon Sep 12 16:59:09 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EEvOP-0007bE-3k
	for v6ops-archive@megatron.ietf.org; Mon, 12 Sep 2005 16:59:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25684
	for <v6ops-archive@ietf.org>; Mon, 12 Sep 2005 16:59:02 -0400 (EDT)
Received: from acb22.internetdsl.tpnet.pl ([83.16.53.22] helo=wbox.de)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1EEvSZ-0004Jm-RU
	for v6ops-archive@ietf.org; Mon, 12 Sep 2005 17:03:29 -0400
From: "Barillaro Gonzalo" <Panek@xrs.net>
To: "Stanfield Adam" <v6ops-archive@ietf.org>
Subject: Re[5]:
Date: Mon, 12 Sep 2005 20:58:54 +0000
Message-ID: <53cc01c5b7dc$1c2096b4$54007977@wbox.de>
X-SA-Do-Not-Rej: Yes
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_1F62_7A89B53D.40CE1F62"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4942.400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4942.400
X-Scan-Module: SMTP[2005.09.09 (2005.06.03)]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa

This is a multi-part message in MIME format.

------=_NextPart_000_1F62_7A89B53D.40CE1F62
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It's recommended for reading Hustler!

Go on, give it a try. You'll sure enjoy it!
SPUR-m [Sperm pills]: http://brachia.com/

Discreet, unmarked packaging.

>>> NB: No prescription required

------=_NextPart_000_1F62_7A89B53D.40CE1F62
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
It's recommended for reading Hustler!
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Go on, give it a try. =
You'll sure=20
enjoy it!<BR>SPUR-m [Sperm pills]: <A=20
href=3D"http://brachia.com/">http://brachia.com/</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Discreet, unmarked=20
packaging.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&gt;&gt;&gt; NB: No =
prescription=20
required<BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_1F62_7A89B53D.40CE1F62--




From Brown@fcbayern.de Tue Sep 13 04:24:39 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EF65l-0000do-El
	for v6ops-archive@megatron.ietf.org; Tue, 13 Sep 2005 04:24:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10088
	for <v6ops-archive@ietf.org>; Tue, 13 Sep 2005 04:24:06 -0400 (EDT)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EF69Y-0004Gx-PJ
	for v6ops-archive@ietf.org; Tue, 13 Sep 2005 04:28:39 -0400
Received: from [222.101.67.229] (helo=epost.de)
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1EF656-0004KC-16
	for v6ops-archive@ietf.org; Tue, 13 Sep 2005 04:23:56 -0400
From: "Lanzi Claudia" <Brown@fcbayern.de>
To: "Baeten Ronny" <v6ops-archive@ietf.org>
Subject: Re[3]:
Date: Tue, 13 Sep 2005 08:23:57 +0000
Message-ID: <393301c5b83c$00585328$54007977@epost.de>
X-SA-Do-Not-Rej: Yes
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_1F62_7A89B53D.40CE1F62"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa

This is a multi-part message in MIME format.

------=_NextPart_000_1F62_7A89B53D.40CE1F62
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Cialis Softtabs - you're always in a good sexual shape.

Go on, give it a try. You'll sure enjoy it!
Cialis Softtabs: http://reproofs.com/now/

Discreet, unmarked packaging.

>>> NB: No prescription required

------=_NextPart_000_1F62_7A89B53D.40CE1F62
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
Cialis Softtabs - you're always in a good sexual shape.
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Go on, give it a try. =
You'll sure=20
enjoy it!<BR>Cialis Softtabs: <A=20
href=3D"http://reproofs.com/now/">http://reproofs.com/now/</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Discreet, unmarked=20
packaging.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&gt;&gt;&gt; NB: No =
prescription=20
required<BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_1F62_7A89B53D.40CE1F62--




From Distel@wish.nl Tue Sep 13 13:14:49 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFEMr-0000pD-Cs
	for v6ops-archive@megatron.ietf.org; Tue, 13 Sep 2005 13:14:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02359
	for <v6ops-archive@ietf.org>; Tue, 13 Sep 2005 13:14:37 -0400 (EDT)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EFER2-0007lc-PK
	for v6ops-archive@ietf.org; Tue, 13 Sep 2005 13:19:16 -0400
Received: from [200.119.211.101] (helo=ucs.com.tw)
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1EFEMV-0000z0-Dy
	for v6ops-archive@ietf.org; Tue, 13 Sep 2005 13:14:31 -0400
From: "Yasak Cem" <Distel@wish.nl>
To: "Middlemas Neil" <v6ops-archive@ietf.org>
Subject: Re:
Date: Tue, 13 Sep 2005 17:14:31 +0000
Message-ID: <421701c5b886$09a99bb1$54007977@ucs.com.tw>
X-SA-Do-Not-Rej: Yes
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_40CE_1F627A89.B53D40CE"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa

This is a multi-part message in MIME format.

------=_NextPart_000_40CE_1F627A89.B53D40CE
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Where are my sweet 16? In a little box over there on the bedside cabinet.

Go on, give it a try. You'll sure enjoy it!
SPUR-m [Cum pills]: http://brachia.com/

Discreet, unmarked packaging.

>>> NB: No prescription required

------=_NextPart_000_40CE_1F627A89.B53D40CE
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
Where are my sweet 16? In a little box over there on the bedside cabinet.
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Go on, give it a try. =
You'll sure=20
enjoy it!<BR>SPUR-m [Cum pills]: <A=20
href=3D"http://brachia.com/">http://brachia.com/</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Discreet, unmarked=20
packaging.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&gt;&gt;&gt; NB: No =
prescription=20
required<BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_40CE_1F627A89.B53D40CE--




From Sinche@uol.com.br Tue Sep 13 13:50:38 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFEvW-0005gk-Rf
	for v6ops-archive@megatron.ietf.org; Tue, 13 Sep 2005 13:50:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03895
	for <v6ops-archive@ietf.org>; Tue, 13 Sep 2005 13:50:24 -0400 (EDT)
Received: from 201-1-182-222.dsl.telesp.net.br ([201.1.182.222] helo=themail.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1EFEzi-000091-6x
	for v6ops-archive@ietf.org; Tue, 13 Sep 2005 13:55:02 -0400
From: "Dario Roberto" <Sinche@uol.com.br>
To: "Andrawes Bassant" <v6ops-archive@ietf.org>
Subject: Re[9]:
Date: Tue, 13 Sep 2005 17:50:16 +0000
Message-ID: <59f901c5b88b$205dc000$54007977@themail.com>
X-SA-Do-Not-Rej: Yes
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_B53D_40CE1F62.7A89B53D"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1437
X-Spam-Score: 2.8 (++)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa

This is a multi-part message in MIME format.

------=_NextPart_000_B53D_40CE1F62.7A89B53D
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Is there sex on Mars? With SPUR-m [Sperm pills] there certainly is! 

Go on, give it a try. You'll sure enjoy it!
SPUR-m [Cum pills]: http://brachia.com/

Discreet, unmarked packaging.

>>> NB: No prescription required

------=_NextPart_000_B53D_40CE1F62.7A89B53D
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
Is there sex on Mars? With SPUR-m [Sperm pills] there certainly is! 
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Go on, give it a try. =
You'll sure=20
enjoy it!<BR>SPUR-m [Cum pills]: <A=20
href=3D"http://brachia.com/">http://brachia.com/</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Discreet, unmarked=20
packaging.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&gt;&gt;&gt; NB: No =
prescription=20
required<BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_B53D_40CE1F62.7A89B53D--




From owner-v6ops@ops.ietf.org Tue Sep 13 14:02:08 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFF6e-0006pF-1U
	for v6ops-archive@megatron.ietf.org; Tue, 13 Sep 2005 14:02:08 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04365
	for <v6ops-archive@lists.ietf.org>; Tue, 13 Sep 2005 14:01:57 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EFF2z-0009gj-DY
	for v6ops-data@psg.com; Tue, 13 Sep 2005 17:58:21 +0000
Received: from [171.71.176.72] (helo=sj-iport-3.cisco.com)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EFF2x-0009gT-P5
	for v6ops@ops.ietf.org; Tue, 13 Sep 2005 17:58:19 +0000
Received: from sj-core-1.cisco.com ([171.71.177.237])
  by sj-iport-3.cisco.com with ESMTP; 13 Sep 2005 10:58:19 -0700
X-IronPort-AV: i="3.97,106,1125903600"; 
   d="scan'208"; a="341280141:sNHT29732160"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j8DHwH4u005416
	for <v6ops@ops.ietf.org>; Tue, 13 Sep 2005 10:58:17 -0700 (PDT)
Received: from [10.32.244.222] (stealth-10-32-244-222.cisco.com [10.32.244.222])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id j8DIAtfF025993
	for <v6ops@ops.ietf.org>; Tue, 13 Sep 2005 11:10:55 -0700
Mime-Version: 1.0 (Apple Message framework v734)
Content-Transfer-Encoding: 7bit
Message-Id: <FD310CEE-864A-4E5C-A430-1EE44054E231@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: v6ops@ops.ietf.org
From: Fred Baker <fred@cisco.com>
Subject: IETF Tools
Date: Tue, 13 Sep 2005 10:58:16 -0700
X-Mailer: Apple Mail (2.734)
DKIM-Signature: a=rsa-sha1;  q=dns; l=737; t=1126635055; x=1127067255;
	c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding;
	d=cisco.com; i=fred@cisco.com; 
	z=Subject:IETF=20Tools|
	From:Fred=20Baker=20<fred@cisco.com>|
	Date:Tue,=2013=20Sep=202005=2010=3A58=3A16=20-0700|
	Content-Type:text/plain=3B=20charset=3DUS-ASCII=3B=20delsp=3Dyes=3B=20format=3Dflowed|
	Content-Transfer-Encoding:7bit;
	b=GI/GAdSMchv+h/K4BJQNEyepqMao9Np+ZiTXzFYIbyImFO67TuSf/Yog5HwIfm+gSErlOIxP
	oAoEwvNepQcjq4ZTwoZ9nOtOpj40G9gfJaAIAAFxNaHHbNLgtdiFDS9OICEO9qPtgdqQPIVV2CF
	vcQKhLU+doga5bVTTcGyl5J0=
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com; dkim=pass (
	message from cisco.com verified; ); 
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Forwarded from Bert Wijnen, with some slight hacking for relevance...

Goto http://tools.ietf.org

If you want to see nits or diffs for any I-D in your WG, you can find  
them on the IETF Tools Page too!
If you go to WG status pages, you get to:

     http://tools.ietf.org/wg/

 From there you can go to your (or any) WG.
See for example:

     http://tools.ietf.org/wg/v6ops/

You can click on dependencies and get to:

     http://rtg.ietf.org/~fenner/ietf/deps/viz/v6ops.pdf

Of you can click on document draft-ietf-v6ops-bb-deployment-scenarios  
and you get to:

     http://tools.ietf.org/wg/v6ops/draft-ietf-v6ops-bb-deployment- 
scenarios/

from there you can see the file itself, any nits (ID-checklist) that  
were found, the diff bnetween all the versions etc.

Very usefull information for authors, WG chairs, WG reviewers  
actually for everyone!

Not sure everyone is really aware of it.




From owner-v6ops@ops.ietf.org Tue Sep 13 14:30:27 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFFY2-0003OB-5b
	for v6ops-archive@megatron.ietf.org; Tue, 13 Sep 2005 14:30:27 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05416
	for <v6ops-archive@lists.ietf.org>; Tue, 13 Sep 2005 14:30:15 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EFFWg-000CPx-MP
	for v6ops-data@psg.com; Tue, 13 Sep 2005 18:29:02 +0000
Received: from [171.68.10.86] (helo=sj-iport-4.cisco.com)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EFFWf-000CPg-U0
	for v6ops@ops.ietf.org; Tue, 13 Sep 2005 18:29:01 +0000
Received: from sj-core-2.cisco.com ([171.71.177.254])
  by sj-iport-4.cisco.com with ESMTP; 13 Sep 2005 11:28:59 -0700
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j8DIStKC009909;
	Tue, 13 Sep 2005 11:28:56 -0700 (PDT)
Received: from [10.32.244.222] (stealth-10-32-244-222.cisco.com [10.32.244.222])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id j8DIfWbI026411;
	Tue, 13 Sep 2005 11:41:32 -0700
In-Reply-To: <431EEF9B.6090806@zurich.ibm.com>
References: <4.3.2.7.2.20050901124115.04916658@strange-brew> <20050902083300.GL17558@login.ecs.soton.ac.uk> <9B968269-D9E5-4F6C-8F17-B5931D8879DE@cisco.com> <431EEF9B.6090806@zurich.ibm.com>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E3AB659A-682A-4581-A320-F49A59DD114C@cisco.com>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, v6ops@ops.ietf.org
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: Proposed Resolution of Issues [1-37]
Date: Tue, 13 Sep 2005 11:28:53 -0700
To: Brian E Carpenter <brc@zurich.ibm.com>
X-Mailer: Apple Mail (2.734)
DKIM-Signature: a=rsa-sha1;  q=dns; l=2035; t=1126636893; x=1127069093;
	c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding;
	d=cisco.com; i=fred@cisco.com; 
	z=Subject:Re=3A=20Proposed=20Resolution=20of=20Issues=20[1-37]|
	From:Fred=20Baker=20<fred@cisco.com>|
	Date:Tue,=2013=20Sep=202005=2011=3A28=3A53=20-0700|
	Content-Type:text/plain=3B=20charset=3DUS-ASCII=3B=20delsp=3Dyes=3B=20format=3Dflowed|
	Content-Transfer-Encoding:7bit;
	b=TviNJPPWvWYzVnF686XLq3tUYCB3lDhuEcoq1Cyl0EIntLq3/o1U5YWPsrh03KgI/epmSL/s
	cpYZQocBFYAmTyI9KDK3vnLseXIj6u06/rwP/mtpiF8RuH0bqsvyQA69zgxsO0pEold7w+fEDwl
	6joHVW3etia6BdyGDbLz14zY=
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com; dkim=pass (
	message from cisco.com verified; ); 
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

So it helps in renumbering by not needing to be renumbered. Same  
would be true if it just happened to be in a different global prefix  
that happened to not need renumbering. I don't think that is an  
argument for or against ULAs, or even an argument about renumbering.  
It is a statement that things that are not at the moment up for  
renumbering probably don't have to be thought about when renumbering.

It seems to me that if one is going to say anything on the topic  
here, one might say that a step one might take early in the game of  
renumbering is to scan the DNS database for names that have more than  
one address, one of which is in the prefix to be renumbered. In any  
such case, one can instantly remove the affected address from the  
name, and all future DNS accesses will be from another prefix (which  
may be a ULA). When one adds the new prefix to DNS, one may include  
these names in doing so. Doing so early will limit the impact of all  
the other steps on the utility of the systems, as the prefix being  
renumbered will not be in use for that system.

ULAs are a special case of that statement, and only apply to local  
systems. And by the way, the above comment doesn't simplify  
renumbering. It adds a step (one which is redundant with a later  
step) and requires memory in some form of what names were affected  
and therefore have to be restored. It makes renumbering more complex.

On Sep 7, 2005, at 6:48 AM, Brian E Carpenter wrote:
> Sometime in the past, I said:
>> If ULAs simplify the procedure of renumbering a network without a  
>> flag day, then there should be several places in the document  
>> where a few sentences of the following form can be added.
>>
>>   "if the old prefix..." or "if the new prefix..."
>>   "is a ULA prefix then"
>>   "...this step may be skipped" or "...this step may be  
>> simplified  <in this way>"
>>   "and it still allows you to renumber a network without a flag  
>> day  for <this> reason."
>>
>> Present me with those sentences, and I will include them.
>
> I don't think any of that applies. My take is that ULAs have the  
> advantage during a renumbering exercise of providing business  
> continuity for *internal* operations - your printers, for example,  
> can have ULAs and are untouched (and their DNS entries are  
> untouched) during the renumbering process. Your internal SMTP  
> system can keep operating without any change to internal DNS. Etc.  
> So it does take a number of hosts off the renumbering list -  
> exactly those hosts that have no external visibility.




From Oliveira@talk21.com Wed Sep 14 00:12:51 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFOde-0005z3-Sl
	for v6ops-archive@megatron.ietf.org; Wed, 14 Sep 2005 00:12:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21637
	for <v6ops-archive@ietf.org>; Wed, 14 Sep 2005 00:12:46 -0400 (EDT)
Received: from 201-1-132-208.dsl.telesp.net.br ([201.1.132.208] helo=myrealbox.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1EFOi8-00057s-JM
	for v6ops-archive@ietf.org; Wed, 14 Sep 2005 00:17:31 -0400
From: "Aviles Xavier" <Oliveira@talk21.com>
To: "Gonzalez Lorena" <v6ops-archive@ietf.org>
Subject: Re[1]:
Date: Wed, 14 Sep 2005 04:13:01 +0000
Message-ID: <1bda01c5b8e2$1e62552a$54007977@myrealbox.com>
X-SA-Do-Not-Rej: Yes
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_1F62_7A89B53D.40CE1F62"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4942.400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4942.400
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa

This is a multi-part message in MIME format.

------=_NextPart_000_1F62_7A89B53D.40CE1F62
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

We don't ask you to trust us when you purchase this medicine. Trust your body!

Go on, give it a try. You'll sure enjoy it!
Cialis Softtabs: http://reproofs.com/now/

Discreet, unmarked packaging.

>>> NB: No prescription required

------=_NextPart_000_1F62_7A89B53D.40CE1F62
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
We don't ask you to trust us when you purchase this medicine. Trust your body!
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Go on, give it a try. =
You'll sure=20
enjoy it!<BR>Cialis Softtabs: <A=20
href=3D"http://reproofs.com/now/">http://reproofs.com/now/</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Discreet, unmarked=20
packaging.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&gt;&gt;&gt; NB: No =
prescription=20
required<BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_1F62_7A89B53D.40CE1F62--




From owner-v6ops@ops.ietf.org Wed Sep 14 02:45:16 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFR11-0005tX-Ni
	for v6ops-archive@megatron.ietf.org; Wed, 14 Sep 2005 02:45:16 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24602
	for <v6ops-archive@lists.ietf.org>; Wed, 14 Sep 2005 02:45:05 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EFQxf-000DIA-K0
	for v6ops-data@psg.com; Wed, 14 Sep 2005 06:41:39 +0000
Received: from [195.212.29.151] (helo=mtagate2.de.ibm.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.50 (FreeBSD))
	id 1EFQxc-000DHq-Ae
	for v6ops@ops.ietf.org; Wed, 14 Sep 2005 06:41:36 +0000
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49])
	by mtagate2.de.ibm.com (8.12.10/8.12.10) with ESMTP id j8E6fWd7142556
	for <v6ops@ops.ietf.org>; Wed, 14 Sep 2005 06:41:32 GMT
Received: from d12av02.megacenter.de.ibm.com (d12av02.megacenter.de.ibm.com [9.149.165.228])
	by d12nrmr1607.megacenter.de.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j8E6fW16096658
	for <v6ops@ops.ietf.org>; Wed, 14 Sep 2005 08:41:32 +0200
Received: from d12av02.megacenter.de.ibm.com (loopback [127.0.0.1])
	by d12av02.megacenter.de.ibm.com (8.12.11/8.13.3) with ESMTP id j8E6fROW021463
	for <v6ops@ops.ietf.org>; Wed, 14 Sep 2005 08:41:27 +0200
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
	by d12av02.megacenter.de.ibm.com (8.12.11/8.12.11) with ESMTP id j8E6fQLo021458;
	Wed, 14 Sep 2005 08:41:26 +0200
Received: from zurich.ibm.com (dyn-9-13-126-126.ge.ch.ibm.com [9.13.126.126])
	by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id IAA54728;
	Wed, 14 Sep 2005 08:41:26 +0200
Message-ID: <4327C614.7090205@zurich.ibm.com>
Date: Wed, 14 Sep 2005 08:41:24 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
CC: Tim Chown <tjc@ecs.soton.ac.uk>, v6ops@ops.ietf.org
Subject: Re: Proposed Resolution of Issues [1-37]
References: <4.3.2.7.2.20050901124115.04916658@strange-brew> <20050902083300.GL17558@login.ecs.soton.ac.uk> <9B968269-D9E5-4F6C-8F17-B5931D8879DE@cisco.com> <431EEF9B.6090806@zurich.ibm.com> <E3AB659A-682A-4581-A320-F49A59DD114C@cisco.com>
In-Reply-To: <E3AB659A-682A-4581-A320-F49A59DD114C@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Fred Baker wrote:
> So it helps in renumbering by not needing to be renumbered. Same  would 
> be true if it just happened to be in a different global prefix  that 
> happened to not need renumbering. I don't think that is an  argument for 
> or against ULAs, or even an argument about renumbering.  It is a 
> statement that things that are not at the moment up for  renumbering 
> probably don't have to be thought about when renumbering.
> 
> It seems to me that if one is going to say anything on the topic  here, 
> one might say that a step one might take early in the game of  
> renumbering is to scan the DNS database for names that have more than  
> one address, one of which is in the prefix to be renumbered. In any  
> such case, one can instantly remove the affected address from the  name, 
> and all future DNS accesses will be from another prefix (which  may be a 
> ULA). When one adds the new prefix to DNS, one may include  these names 
> in doing so. Doing so early will limit the impact of all  the other 
> steps on the utility of the systems, as the prefix being  renumbered 
> will not be in use for that system.
> 
> ULAs are a special case of that statement, and only apply to local  
> systems.

That's true. Because IPv6 networks may have multiple simultaneous prefixes
as a matter of course, that check always seems to be needed.

> And by the way, the above comment doesn't simplify  
> renumbering. It adds a step (one which is redundant with a later  step) 
> and requires memory in some form of what names were affected  and 
> therefore have to be restored. It makes renumbering more complex.

It's the observation that a site may have N prefixes only some of
which are being renumbered that adds complexity, I think. In this respect
I don't see that a ULA prefix is any different from an RIR-allocated
prefix that is only used internally - i.e. I see no architectural
change here. (This is another face of the assertion that ULAs behave
like global addresses.)

     Brian

> 
> On Sep 7, 2005, at 6:48 AM, Brian E Carpenter wrote:
> 
>> Sometime in the past, I said:
>>
>>> If ULAs simplify the procedure of renumbering a network without a  
>>> flag day, then there should be several places in the document  where 
>>> a few sentences of the following form can be added.
>>>
>>>   "if the old prefix..." or "if the new prefix..."
>>>   "is a ULA prefix then"
>>>   "...this step may be skipped" or "...this step may be  simplified  
>>> <in this way>"
>>>   "and it still allows you to renumber a network without a flag  day  
>>> for <this> reason."
>>>
>>> Present me with those sentences, and I will include them.
>>
>>
>> I don't think any of that applies. My take is that ULAs have the  
>> advantage during a renumbering exercise of providing business  
>> continuity for *internal* operations - your printers, for example,  
>> can have ULAs and are untouched (and their DNS entries are  untouched) 
>> during the renumbering process. Your internal SMTP  system can keep 
>> operating without any change to internal DNS. Etc.  So it does take a 
>> number of hosts off the renumbering list -  exactly those hosts that 
>> have no external visibility.
> 
> 





From owner-v6ops@ops.ietf.org Wed Sep 14 04:30:49 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFSfJ-0003yN-46
	for v6ops-archive@megatron.ietf.org; Wed, 14 Sep 2005 04:30:49 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28171
	for <v6ops-archive@lists.ietf.org>; Wed, 14 Sep 2005 04:30:46 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EFSdp-000KyT-Oi
	for v6ops-data@psg.com; Wed, 14 Sep 2005 08:29:17 +0000
Received: from [152.78.70.1] (helo=raven.ecs.soton.ac.uk)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EFSdo-000KyE-T5
	for v6ops@ops.ietf.org; Wed, 14 Sep 2005 08:29:17 +0000
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id j8E8TFiN000772
	for <v6ops@ops.ietf.org>; Wed, 14 Sep 2005 09:29:15 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id JAA08496
	for <v6ops@ops.ietf.org>; Wed, 14 Sep 2005 09:29:01 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id j8E8T1G15393
	for v6ops@ops.ietf.org; Wed, 14 Sep 2005 09:29:01 +0100
Date: Wed, 14 Sep 2005 09:29:01 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: v6ops@ops.ietf.org
Subject: Re: IETF Tools
Message-ID: <20050914082901.GG14764@login.ecs.soton.ac.uk>
Mail-Followup-To: v6ops@ops.ietf.org
References: <FD310CEE-864A-4E5C-A430-1EE44054E231@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FD310CEE-864A-4E5C-A430-1EE44054E231@cisco.com>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-MailScanner-From: tjc@smtp.ecs.soton.ac.uk
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

On Tue, Sep 13, 2005 at 10:58:16AM -0700, Fred Baker wrote:
> 
> Very usefull information for authors, WG chairs, WG reviewers  
> actually for everyone!
> 
> Not sure everyone is really aware of it.

The effort behind the scenes with IETF tools in the last 12 months has
been fantastic and is much appreciated.   Kudos to all involved :)

-- 
Tim/::1






From Auger@grooveasia.com Wed Sep 14 09:29:00 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFXJs-00029N-R5
	for v6ops-archive@megatron.ietf.org; Wed, 14 Sep 2005 09:29:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10617
	for <v6ops-archive@ietf.org>; Wed, 14 Sep 2005 09:28:58 -0400 (EDT)
Received: from [85.103.49.1] (helo=gedris.org)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1EFXOS-00020X-Rv
	for v6ops-archive@ietf.org; Wed, 14 Sep 2005 09:33:46 -0400
From: "Morais Susana" <Auger@grooveasia.com>
To: "Tenerina Casperina" <v6ops-archive@ietf.org>
Subject: Re:
Date: Wed, 14 Sep 2005 13:29:03 +0000
Message-ID: <17b701c5b930$00428814$54007977@gedris.org>
X-SA-Do-Not-Rej: Yes
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_40CE_1F627A89.B53D40CE"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Antivirus: avast! (VPS 0537-1, 14.09.2005), Outbound message
X-Antivirus-Status: Clean
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa

This is a multi-part message in MIME format.

------=_NextPart_000_40CE_1F627A89.B53D40CE
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Enjoy great benefits of MORE-SIZE with your partner!

Go on, give it a try. You'll sure enjoy it!
MORE-SIZE: http://efficacies.net/more/

Discreet, unmarked packaging.

>>> NB: No prescription required

------=_NextPart_000_40CE_1F627A89.B53D40CE
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
Enjoy great benefits of MORE-SIZE with your partner!
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Go on, give it a try. =
You'll sure=20
enjoy it!<BR>MORE-SIZE: <A=20
href=3D"http://efficacies.net/more/">http://efficacies.net/more/</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Discreet, unmarked=20
packaging.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&gt;&gt;&gt; NB: No =
prescription=20
required<BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_40CE_1F627A89.B53D40CE--




From Morais@wish.nl Wed Sep 14 15:07:36 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFcbX-0002TG-T4
	for v6ops-archive@megatron.ietf.org; Wed, 14 Sep 2005 15:07:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27119
	for <v6ops-archive@ietf.org>; Wed, 14 Sep 2005 15:07:34 -0400 (EDT)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EFcgB-00024T-Qq
	for v6ops-archive@ietf.org; Wed, 14 Sep 2005 15:12:25 -0400
Received: from ajx92.neoplus.adsl.tpnet.pl ([83.26.1.92] helo=webaddressbook.com)
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1EFbjT-0004zF-W9
	for v6ops-archive@ietf.org; Wed, 14 Sep 2005 14:11:44 -0400
From: "Rgevsky Mihas" <Morais@wish.nl>
To: "Enas Lovely" <v6ops-archive@ietf.org>
Subject: Re[6]:
Date: Wed, 14 Sep 2005 19:07:31 +0000
Message-ID: <41f101c5b95f$0d89ee80$54007977@webaddressbook.com>
X-SA-Do-Not-Rej: Yes
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_7A89_B53D40CE.1F627A89"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1441
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Scan-Module: SMTP[2005.09.14 (2005.06.03)]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa

This is a multi-part message in MIME format.

------=_NextPart_000_7A89_B53D40CE.1F627A89
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Tantric sex exists - with Cialis Softtabs!

Go on, give it a try. You'll sure enjoy it!
Cialis Softtabs: http://unglazed.net/now/

Discreet, unmarked packaging.

>>> NB: No prescription required

------=_NextPart_000_7A89_B53D40CE.1F627A89
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
Tantric sex exists - with Cialis Softtabs!
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Go on, give it a try. =
You'll sure=20
enjoy it!<BR>Cialis Softtabs: <A=20
href=3D"http://unglazed.net/now/">http://unglazed.net/now/</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Discreet, unmarked=20
packaging.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&gt;&gt;&gt; NB: No =
prescription=20
required<BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_7A89_B53D40CE.1F627A89--




From Kashkarov@etang.com Thu Sep 15 04:43:30 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFpL8-0005He-Bp
	for v6ops-archive@megatron.ietf.org; Thu, 15 Sep 2005 04:43:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27849
	for <v6ops-archive@ietf.org>; Thu, 15 Sep 2005 04:43:27 -0400 (EDT)
Received: from vectra2.veo.pl ([213.25.22.174] helo=eastmail.com)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1EFpPo-0001Pl-Tk
	for v6ops-archive@ietf.org; Thu, 15 Sep 2005 04:48:25 -0400
From: "Puga Jacobo" <Kashkarov@etang.com>
To: "Artyukh Vitaliy" <v6ops-archive@ietf.org>
Subject: Re[9]:
Date: Thu, 15 Sep 2005 08:43:25 +0000
Message-ID: <7c0901c5b9d1$01699a4c$54007977@eastmail.com>
X-SA-Do-Not-Rej: Yes
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_B53D_40CE1F62.7A89B53D"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1437
X-Antivirus: avast! (VPS 0537-1, 2005-09-14), Outbound message
X-Antivirus-Status: Clean
X-Spam-Score: 4.8 (++++)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa

This is a multi-part message in MIME format.

------=_NextPart_000_B53D_40CE1F62.7A89B53D
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

MORE-SIZE is the fastest and easiest way to achieve the length and girth of penis that you desire

Go on, give it a try. You'll sure enjoy it!
MORE-SIZE: http://efficacies.net/more/

Discreet, unmarked packaging.

>>> NB: No prescription required

------=_NextPart_000_B53D_40CE1F62.7A89B53D
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
MORE-SIZE is the fastest and easiest way to achieve the length and girth of penis that you desire
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Go on, give it a try. =
You'll sure=20
enjoy it!<BR>MORE-SIZE: <A=20
href=3D"http://efficacies.net/more/">http://efficacies.net/more/</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Discreet, unmarked=20
packaging.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&gt;&gt;&gt; NB: No =
prescription=20
required<BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_B53D_40CE1F62.7A89B53D--




From Niculae@371.net Thu Sep 15 10:36:57 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EFurB-0000r3-Pt
	for v6ops-archive@megatron.ietf.org; Thu, 15 Sep 2005 10:36:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14903
	for <v6ops-archive@ietf.org>; Thu, 15 Sep 2005 10:36:54 -0400 (EDT)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EFuvy-0002lo-PG
	for v6ops-archive@ietf.org; Thu, 15 Sep 2005 10:41:56 -0400
Received: from homeinternet-pv.infos.cz ([193.179.148.53] helo=163.com)
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1EFuqs-0000cy-Q7
	for v6ops-archive@ietf.org; Thu, 15 Sep 2005 10:36:39 -0400
From: "Klevakin Eugene" <Niculae@371.net>
To: "Cavlak Bayram" <v6ops-archive@ietf.org>
Subject: Re[5]:
Date: Thu, 15 Sep 2005 14:36:39 +0000
Message-ID: <2da301c5ba02$00448f86$54007977@163.com>
X-SA-Do-Not-Rej: Yes
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_1F62_7A89B53D.40CE1F62"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Antivirus: avast! (VPS 0537-1, 14.09.2005), Outbound message
X-Antivirus-Status: Clean
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa

This is a multi-part message in MIME format.

------=_NextPart_000_1F62_7A89B53D.40CE1F62
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It's recommended for reading Hustler!

Go on, give it a try. You'll sure enjoy it!
SPUR-m [Sperm pills]: http://rehire.net/

Discreet, unmarked packaging.

>>> NB: No prescription required

------=_NextPart_000_1F62_7A89B53D.40CE1F62
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
It's recommended for reading Hustler!
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Go on, give it a try. =
You'll sure=20
enjoy it!<BR>SPUR-m [Sperm pills]: <A=20
href=3D"http://rehire.net/">http://rehire.net/</A></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Discreet, unmarked=20
packaging.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&gt;&gt;&gt; NB: No =
prescription=20
required<BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_1F62_7A89B53D.40CE1F62--




From owner-v6ops@ops.ietf.org Thu Sep 15 17:57:01 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EG1j3-0001ZA-0G
	for v6ops-archive@megatron.ietf.org; Thu, 15 Sep 2005 17:57:01 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12881
	for <v6ops-archive@lists.ietf.org>; Thu, 15 Sep 2005 17:56:57 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EG1et-0009Er-LA
	for v6ops-data@psg.com; Thu, 15 Sep 2005 21:52:43 +0000
Received: from [171.71.176.70] (helo=sj-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EG1es-0009E7-C1
	for v6ops@ops.ietf.org; Thu, 15 Sep 2005 21:52:42 +0000
Received: from sj-core-2.cisco.com ([171.71.177.254])
  by sj-iport-1.cisco.com with ESMTP; 15 Sep 2005 14:52:42 -0700
X-IronPort-AV: i="3.97,114,1125903600"; 
   d="scan'208"; a="660080300:sNHT36990466"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j8FLqaKC000767;
	Thu, 15 Sep 2005 14:52:36 -0700 (PDT)
Received: from [10.32.244.222] (stealth-10-32-244-222.cisco.com [10.32.244.222])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id j8FM58HP018077;
	Thu, 15 Sep 2005 15:05:08 -0700
In-Reply-To: <20050915185626.GF15202@isi.edu>
References: <20050915185626.GF15202@isi.edu>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C625CE06-58E5-4961-8435-A84E92D64701@cisco.com>
Cc: lear@cisco.com, Ralph Droms <rdroms@cisco.com>,
        David Kessens <david.kessens@nokia.com>,
        Bert Wijnen <bwijnen@lucent.com>, v6ops@ops.ietf.org
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: draft-ietf-v6ops-renumbering-procedure-05.txt
Date: Thu, 15 Sep 2005 14:52:36 -0700
To: RFC Editor <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.734)
DKIM-Signature: a=rsa-sha1;  q=dns; l=1646; t=1126821908; x=1127254108;
	c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding;
	d=cisco.com; i=fred@cisco.com; 
	z=Subject:Re=3A=20draft-ietf-v6ops-renumbering-procedure-05.txt|
	From:Fred=20Baker=20<fred@cisco.com>|
	Date:Thu,=2015=20Sep=202005=2014=3A52=3A36=20-0700|
	Content-Type:text/plain=3B=20charset=3DUS-ASCII=3B=20delsp=3Dyes=3B=20format=3Dflowed|
	Content-Transfer-Encoding:7bit;
	b=Kpv4ZlMQgpNL424SfPxOiDEN7TxaBxG6gqVOyWeabfs+BTCvxwge9FV+ajqNdkPz2vLVcrgs
	M57EPV3Pc5O26n+oXGMLj9otUBVHsgy8c5V4fR3QZajEqDftB4JA/j3Z82HVyOYGd4e9TEFGSDE
	54oWlN91F/teV7RqKUV9sWMg=
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com; dkim=pass (
	message from cisco.com verified; ); 
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

My compatriots may disagree with me; I am answering for myself.

On Sep 15, 2005, at 11:56 AM, RFC Editor wrote:

> Authors,
>
> While checking the references within
> <draft-ietf-v6ops-renumbering-procedure-05.txt>, we noticed a
> reference to RFC 2535.  However, RFC 2535 has been obsoleted by RFCs
> 4033, 4034, and 4035.  Is it appropriate to replace instances of
> [RFC2535] with [RFC4033][RFC4034][RFC4035]?

Yes, I should think so. Those RFCs were published after the  
renumbering document had entered the RFC Editor's queue and escaped  
our notice.

> We also have a few other questions.
>
>
> 1) Would you object to our changing the following:
>
>    It may be considered an update to [RFC2072].
>
> To:
>
>    This document updates [RFC2072].

That works for me

> 2) We have changed the following:
>
>    Use of StateLess Address Configuration [RFC2462] (SLAC)...
>
> To:
>
>    Use of StateLess Address Autoconfiguration (SLAC) [RFC2462]...
>
> This seemed to be consistent with the title of RFC 2462 and with the
> SLAC definition in section 1.2.  Please let us know if this is
> incorrect.

That works for me

> 3) Could you please clarify the following text:
>
>    A special consideration applies when some devices are only
>    occasionally used; the administration must allow sufficiently long
>    in Section 2.6 to ensure that their likelihood of detection is
>    sufficiently high.
>
> Must allow a sufficient length of time?

Yes, the text

    A special consideration applies when some devices are only
    occasionally used; the administration must allow a sufficient
    length of time in Section 2.6 to ensure that their likelihood
    of detection is sufficiently high.

conveys the intended meaning. That said, it might be worthwhile to  
instead say

    A special consideration applies when some devices are only
    occasionally used; the administration must allow a sufficient
    length of time in Section 2.6 or apply other verification
    procedures to ensure that their likelihood of detection is
    sufficiently high.




From owner-v6ops@ops.ietf.org Sat Sep 17 07:39:40 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EGb2i-000172-As
	for v6ops-archive@megatron.ietf.org; Sat, 17 Sep 2005 07:39:40 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08584
	for <v6ops-archive@lists.ietf.org>; Sat, 17 Sep 2005 07:39:39 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EGaxH-0009tg-2D
	for v6ops-data@psg.com; Sat, 17 Sep 2005 11:34:03 +0000
Received: from [209.71.226.4] (helo=ex.hexago.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.50 (FreeBSD))
	id 1EGaxE-0009tN-Jo
	for v6ops@ops.ietf.org; Sat, 17 Sep 2005 11:34:00 +0000
Received: from [127.0.0.1] (retro.hexago.com [209.71.226.5])
	by ex.hexago.com ( hexago/8.13.4) with ESMTP id j8HBWUGc063230
	for <v6ops@ops.ietf.org>; Sat, 17 Sep 2005 07:32:31 -0400 (EDT)
	(envelope-from marc.blanchet@hexago.com)
Mime-Version: 1.0 (Apple Message framework v734)
References: <E1EGMDi-0002yz-4x@newodin.ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <706771F5-064C-4610-B5B2-00D8AC1FDC6D@hexago.com>
Content-Transfer-Encoding: quoted-printable
From: Marc Blanchet <marc.blanchet@hexago.com>
Subject: Fwd: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt 
Date: Sat, 17 Sep 2005 07:32:20 -0400
To: v6ops@ops.ietf.org
X-Mailer: Apple Mail (2.734)
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hi,
  was discussed many times in many forums: what ipv6 routes to =20
filter. operational.
First cut. Please comment.  I know one debatable issue... that will =20
be raised!

Marc.

D=E9but du message r=E9exp=E9di=E9 :

> De : Internet-Drafts@ietf.org
> Date : 16 septembre 2005 15:50:02 HAE
> =C0 : i-d-announce@ietf.org
> Objet : I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt
> R=E9pondre =E0 : internet-drafts@ietf.org
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts =20
> directories.
>
>
>     Title        : IPv6 Routing Policies Guidelines
>     Author(s)    : M. Blanchet
>     Filename    : draft-blanchet-v6ops-routing-guidelines-00.txt
>     Pages        : 7
>     Date        : 2005-9-16
>
>    Guidelines on how to handle IPv6 routes are needed for operators of
>    networks, either providers or enterprises.  This document is a
>    followup of RFC2772 work but for the production IPv6 Internet.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-blanchet-v6ops-routing-=20
> guidelines-00.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body =20=

> of the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
>
> Internet-Drafts are also available by anonymous FTP. Login with the =20=

> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
>     "get draft-blanchet-v6ops-routing-guidelines-00.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
>     mailserv@ietf.org.
> In the body type:
>     "FILE /internet-drafts/draft-blanchet-v6ops-routing-=20
> guidelines-00.txt".
>
> NOTE:    The mail server at ietf.org can return the document in
>     MIME-encoded form by using the "mpack" utility.  To use this
>     feature, insert the command "ENCODING mime" before the "FILE"
>     command.  To decode the response(s), you will need "munpack" or
>     a MIME-compliant mail reader.  Different MIME-compliant mail =20
> readers
>     exhibit different behavior, especially when dealing with
>     "multipart" MIME messages (i.e. documents which have been split
>     up into multiple messages), so check your local documentation on
>     how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID: <2005-9-16110727.I-D@ietf.org>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce
>





From owner-v6ops@ops.ietf.org Sat Sep 17 21:06:44 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EGndj-000283-SF
	for v6ops-archive@megatron.ietf.org; Sat, 17 Sep 2005 21:06:44 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12955
	for <v6ops-archive@lists.ietf.org>; Sat, 17 Sep 2005 21:06:41 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EGnaN-00008P-JA
	for v6ops-data@psg.com; Sun, 18 Sep 2005 01:03:15 +0000
Received: from [208.17.35.59] (helo=paoakoavas10.cable.comcast.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.50 (FreeBSD))
	id 1EGnaL-000082-W4
	for v6ops@ops.ietf.org; Sun, 18 Sep 2005 01:03:14 +0000
Received: from ([10.20.9.172])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH3.13540071;
	Sat, 17 Sep 2005 21:02:58 -0400
Received: from PACDCEXCMB01.cable.comcast.com ([10.20.10.113]) by PACDCEXCSMTP01.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.211);
	 Sat, 17 Sep 2005 21:02:56 -0400
X-MIMEOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt 
Date: Sat, 17 Sep 2005 21:01:16 -0400
Message-ID: <6EEEACD9D7F52940BEE26F5467C02C730DFA3E@PACDCEXCMB01.cable.comcast.com>
Thread-Topic: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt 
Thread-Index: AcW7gAIhlewX6N3HQtqttbQRJH0rEAAbHbdx
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: "Marc Blanchet" <marc.blanchet@hexago.com>, <v6ops@ops.ietf.org>
X-OriginalArrivalTime: 18 Sep 2005 01:02:56.0811 (UTC) FILETIME=[B4B11FB0:01C5BBEC]
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Marc,
=20
How does this differ from RFC2772? Do you feel a need to update it?
=20
---------------------------------
Alain Durand
Director - IPv6 architect

________________________________

From: owner-v6ops@ops.ietf.org on behalf of Marc Blanchet
Sent: Sat 9/17/2005 7:32 AM
To: v6ops@ops.ietf.org
Subject: Fwd: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt=20



Hi,
  was discussed many times in many forums: what ipv6 routes to=20
filter. operational.
First cut. Please comment.  I know one debatable issue... that will=20
be raised!

Marc.

D=E9but du message r=E9exp=E9di=E9 :

> De : Internet-Drafts@ietf.org
> Date : 16 septembre 2005 15:50:02 HAE
> =C0 : i-d-announce@ietf.org
> Objet : I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt
> R=E9pondre =E0 : internet-drafts@ietf.org
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts=20
> directories.
>
>
>     Title        : IPv6 Routing Policies Guidelines
>     Author(s)    : M. Blanchet
>     Filename    : draft-blanchet-v6ops-routing-guidelines-00.txt
>     Pages        : 7
>     Date        : 2005-9-16
>
>    Guidelines on how to handle IPv6 routes are needed for operators of
>    networks, either providers or enterprises.  This document is a
>    followup of RFC2772 work but for the production IPv6 Internet.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-blanchet-v6ops-routing-
> guidelines-00.txt
>
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body=20
> of the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>
>
> Internet-Drafts are also available by anonymous FTP. Login with the=20
> username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
>     "get draft-blanchet-v6ops-routing-guidelines-00.txt".
>
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> Internet-Drafts can also be obtained by e-mail.
>
> Send a message to:
>     mailserv@ietf.org.
> In the body type:
>     "FILE /internet-drafts/draft-blanchet-v6ops-routing-
> guidelines-00.txt".
>
> NOTE:    The mail server at ietf.org can return the document in
>     MIME-encoded form by using the "mpack" utility.  To use this
>     feature, insert the command "ENCODING mime" before the "FILE"
>     command.  To decode the response(s), you will need "munpack" or
>     a MIME-compliant mail reader.  Different MIME-compliant mail=20
> readers
>     exhibit different behavior, especially when dealing with
>     "multipart" MIME messages (i.e. documents which have been split
>     up into multiple messages), so check your local documentation on
>     how to manipulate these messages.
>
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> Content-Type: text/plain
> Content-ID: <2005-9-16110727.I-D@ietf.org>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/i-d-announce
>








From owner-v6ops@ops.ietf.org Mon Sep 19 02:15:31 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EHEw6-0006Bl-R0
	for v6ops-archive@megatron.ietf.org; Mon, 19 Sep 2005 02:15:31 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00170
	for <v6ops-archive@lists.ietf.org>; Mon, 19 Sep 2005 02:15:29 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EHEr2-0004vP-RS
	for v6ops-data@psg.com; Mon, 19 Sep 2005 06:10:16 +0000
Received: from [193.94.160.1] (helo=netcore.fi)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EHEqz-0004vD-Pi
	for v6ops@ops.ietf.org; Mon, 19 Sep 2005 06:10:14 +0000
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id j8J6A1i27685;
	Mon, 19 Sep 2005 09:10:01 +0300
Date: Mon, 19 Sep 2005 09:10:01 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: "Durand, Alain" <Alain_Durand@cable.comcast.com>
cc: Marc Blanchet <marc.blanchet@hexago.com>, v6ops@ops.ietf.org
Subject: RE: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt 
In-Reply-To: <6EEEACD9D7F52940BEE26F5467C02C730DFA3E@PACDCEXCMB01.cable.comcast.com>
Message-ID: <Pine.LNX.4.61.0509190859020.27448@netcore.fi>
References: <6EEEACD9D7F52940BEE26F5467C02C730DFA3E@PACDCEXCMB01.cable.comcast.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

Note: the next rev of this doc (if there is one) should maybe be 
forwarded for comments on the ipv6-ops@lists.cluenet.de list.

On Sat, 17 Sep 2005, Durand, Alain wrote:
> How does this differ from RFC2772? Do you feel a need to update it?

RFC2772 includes guidelines for *6bone*.  This is offering guidelines 
for more than that.  In that light, if we feel the IETF is the right 
place to give guidance on this, updating is certainly needed.

As already noted in the IETF/ipv6 lists, it's an open question to what 
degree and how strong guidance the IETF should (or even could) give to 
the operators.

It seems that if the IETF would want to pursue this work, the 
discussion would need to be recast in the manner "You should 
considering doing [this].  This is why it may or may not make sense". 
As we learned from the DNS configuration debates at DNSOP (though the 
situation is a bit difficult), getting to a consensus could be very 
difficult.

A couple of specific comments:

  - the global unicast address recommendations are (IMHO) way too lax. 
Even some part of 'strict' filters in 
http://www.space.net/~gert/RIPE/ipv6-filters.html could be stricter. 
In any case, that URL should also be referred.  This is an example of 
the case why getting CONSENSUS on a document like this is going to be 
very difficult.  Many folks don't see a problem w/ putting /48 junk 
etc. in the routing tables, others do.  This doc would/could then 
become a political battleground in the v6 operations community..

  - the uppercase keywords are inappropriate and should be removed

  - the doc should probably make RFC2772 historic


-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From owner-v6ops@ops.ietf.org Mon Sep 19 04:26:42 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EHGz2-0007iB-0U
	for v6ops-archive@megatron.ietf.org; Mon, 19 Sep 2005 04:26:42 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05832
	for <v6ops-archive@lists.ietf.org>; Mon, 19 Sep 2005 04:26:37 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EHGwB-000Fnv-F8
	for v6ops-data@psg.com; Mon, 19 Sep 2005 08:23:43 +0000
Received: from [152.78.70.1] (helo=raven.ecs.soton.ac.uk)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EHGw9-000Fnh-B5
	for v6ops@ops.ietf.org; Mon, 19 Sep 2005 08:23:41 +0000
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id j8J8NdiN018199
	for <v6ops@ops.ietf.org>; Mon, 19 Sep 2005 09:23:39 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id JAA05545
	for <v6ops@ops.ietf.org>; Mon, 19 Sep 2005 09:23:32 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id j8J8NWG06962
	for v6ops@ops.ietf.org; Mon, 19 Sep 2005 09:23:32 +0100
Date: Mon, 19 Sep 2005 09:23:32 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: v6ops@ops.ietf.org
Subject: Re: Fwd: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt
Message-ID: <20050919082332.GF6059@login.ecs.soton.ac.uk>
Mail-Followup-To: v6ops@ops.ietf.org
References: <E1EGMDi-0002yz-4x@newodin.ietf.org> <706771F5-064C-4610-B5B2-00D8AC1FDC6D@hexago.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <706771F5-064C-4610-B5B2-00D8AC1FDC6D@hexago.com>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-MailScanner-From: tjc@smtp.ecs.soton.ac.uk
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id EAA05832

I agree this is a useful operational discussion to be had, and v6ops is
the right place for it.   I'm not sure why Bill was confused by the
intended target wg.

Tim

On Sat, Sep 17, 2005 at 07:32:20AM -0400, Marc Blanchet wrote:
> Hi,
>  was discussed many times in many forums: what ipv6 routes to =20
> filter. operational.
> First cut. Please comment.  I know one debatable issue... that will =20
> be raised!
>=20
> Marc.
>=20
> D=E9but du message r=E9exp=E9di=E9 :
>=20
> >De : Internet-Drafts@ietf.org
> >Date : 16 septembre 2005 15:50:02 HAE
> >=C0 : i-d-announce@ietf.org
> >Objet : I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt
> >R=E9pondre =E0 : internet-drafts@ietf.org
> >
> >
> >A New Internet-Draft is available from the on-line Internet-Drafts =20
> >directories.
> >
> >
> >    Title        : IPv6 Routing Policies Guidelines
> >    Author(s)    : M. Blanchet
> >    Filename    : draft-blanchet-v6ops-routing-guidelines-00.txt
> >    Pages        : 7
> >    Date        : 2005-9-16
> >
> >   Guidelines on how to handle IPv6 routes are needed for operators of
> >   networks, either providers or enterprises.  This document is a
> >   followup of RFC2772 work but for the production IPv6 Internet.
> >
> >A URL for this Internet-Draft is:
> >http://www.ietf.org/internet-drafts/draft-blanchet-v6ops-routing-=20
> >guidelines-00.txt
> >
> >To remove yourself from the I-D Announcement list, send a message to
> >i-d-announce-request@ietf.org with the word unsubscribe in the body =20
> >of the message.
> >You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> >to change your subscription settings.
> >
> >
> >Internet-Drafts are also available by anonymous FTP. Login with the =20
> >username
> >"anonymous" and a password of your e-mail address. After logging in,
> >type "cd internet-drafts" and then
> >    "get draft-blanchet-v6ops-routing-guidelines-00.txt".
> >
> >A list of Internet-Drafts directories can be found in
> >http://www.ietf.org/shadow.html
> >or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >
> >Internet-Drafts can also be obtained by e-mail.
> >
> >Send a message to:
> >    mailserv@ietf.org.
> >In the body type:
> >    "FILE /internet-drafts/draft-blanchet-v6ops-routing-=20
> >guidelines-00.txt".
> >
> >NOTE:    The mail server at ietf.org can return the document in
> >    MIME-encoded form by using the "mpack" utility.  To use this
> >    feature, insert the command "ENCODING mime" before the "FILE"
> >    command.  To decode the response(s), you will need "munpack" or
> >    a MIME-compliant mail reader.  Different MIME-compliant mail =20
> >readers
> >    exhibit different behavior, especially when dealing with
> >    "multipart" MIME messages (i.e. documents which have been split
> >    up into multiple messages), so check your local documentation on
> >    how to manipulate these messages.
> >
> >
> >Below is the data which will enable a MIME compliant mail reader
> >implementation to automatically retrieve the ASCII version of the
> >Internet-Draft.
> >Content-Type: text/plain
> >Content-ID: <2005-9-16110727.I-D@ietf.org>
> >
> >_______________________________________________
> >I-D-Announce mailing list
> >I-D-Announce@ietf.org
> >https://www1.ietf.org/mailman/listinfo/i-d-announce
> >
>=20
>=20

--=20
Tim/::1






From owner-v6ops@ops.ietf.org Mon Sep 19 04:31:49 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EHH41-0000e7-3I
	for v6ops-archive@megatron.ietf.org; Mon, 19 Sep 2005 04:31:49 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06060
	for <v6ops-archive@lists.ietf.org>; Mon, 19 Sep 2005 04:31:46 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EHH2u-000GJO-Ez
	for v6ops-data@psg.com; Mon, 19 Sep 2005 08:30:40 +0000
Received: from [152.78.70.1] (helo=raven.ecs.soton.ac.uk)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EHH2s-000GId-NS
	for v6ops@ops.ietf.org; Mon, 19 Sep 2005 08:30:39 +0000
Received: from magpie.ecs.soton.ac.uk (magpie.ecs.soton.ac.uk [152.78.68.131])
	by raven.ecs.soton.ac.uk (8.12.10/8.12.10) with ESMTP id j8J8UbiN018406
	for <v6ops@ops.ietf.org>; Mon, 19 Sep 2005 09:30:37 +0100 (BST)
Received: from login.ecs.soton.ac.uk (IDENT:root@login [152.78.68.162])
	by magpie.ecs.soton.ac.uk (8.9.3/8.9.3) with ESMTP id JAA06515
	for <v6ops@ops.ietf.org>; Mon, 19 Sep 2005 09:30:22 +0100 (BST)
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.11.6/8.11.6) id j8J8UMJ07109
	for v6ops@ops.ietf.org; Mon, 19 Sep 2005 09:30:22 +0100
Date: Mon, 19 Sep 2005 09:30:22 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: v6ops@ops.ietf.org
Subject: Re: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt
Message-ID: <20050919083022.GH6059@login.ecs.soton.ac.uk>
Mail-Followup-To: v6ops@ops.ietf.org
References: <6EEEACD9D7F52940BEE26F5467C02C730DFA3E@PACDCEXCMB01.cable.comcast.com> <Pine.LNX.4.61.0509190859020.27448@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.61.0509190859020.27448@netcore.fi>
User-Agent: Mutt/1.4i
X-MailScanner-Information: Please contact helpdesk@ecs.soton.ac.uk for more information
X-ECS-MailScanner: Found to be clean
X-MailScanner-From: tjc@smtp.ecs.soton.ac.uk
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

On Mon, Sep 19, 2005 at 09:10:01AM +0300, Pekka Savola wrote:
> 
> RFC2772 includes guidelines for *6bone*.  This is offering guidelines 
> for more than that.  In that light, if we feel the IETF is the right 
> place to give guidance on this, updating is certainly needed.

Well yes, one recommendation is now on filtering 3ffe::/16 prefixes, 
at least from 06/06/06 ;)

> As already noted in the IETF/ipv6 lists, it's an open question to what 
> degree and how strong guidance the IETF should (or even could) give to 
> the operators.

We have BCP in many areas.   As with everything else, nothing can be forced,
so Bill can continue to do as he pleases.

>  - the uppercase keywords are inappropriate and should be removed

I agree.  It is just guidelines.

-- 
Tim/::1




From owner-v6ops@ops.ietf.org Mon Sep 19 08:50:32 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EHL6N-0001PT-S6
	for v6ops-archive@megatron.ietf.org; Mon, 19 Sep 2005 08:50:32 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18572
	for <v6ops-archive@lists.ietf.org>; Mon, 19 Sep 2005 08:50:29 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EHL46-000Cxm-JZ
	for v6ops-data@psg.com; Mon, 19 Sep 2005 12:48:10 +0000
Received: from [209.71.226.4] (helo=ex.hexago.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.50 (FreeBSD))
	id 1EHL44-000CxS-BI
	for v6ops@ops.ietf.org; Mon, 19 Sep 2005 12:48:08 +0000
Received: from [209.71.226.82] (82.226.71.209.hexago.com [209.71.226.82] (may be forged))
	by ex.hexago.com ( hexago/8.13.4) with ESMTP id j8JCkPjQ084056;
	Mon, 19 Sep 2005 08:46:26 -0400 (EDT)
	(envelope-from marc.blanchet@hexago.com)
In-Reply-To: <Pine.LNX.4.61.0509190859020.27448@netcore.fi>
References: <6EEEACD9D7F52940BEE26F5467C02C730DFA3E@PACDCEXCMB01.cable.comcast.com> <Pine.LNX.4.61.0509190859020.27448@netcore.fi>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <339F3159-DCD2-4EA1-95D7-54836EC9AE1F@hexago.com>
Cc: "Durand, Alain" <Alain_Durand@cable.comcast.com>, v6ops@ops.ietf.org
Content-Transfer-Encoding: quoted-printable
From: Marc Blanchet <marc.blanchet@hexago.com>
Subject: Re: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt 
Date: Mon, 19 Sep 2005 08:45:58 -0400
To: Pekka Savola <pekkas@netcore.fi>
X-Mailer: Apple Mail (2.734)
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Le 05-09-19 =E0 02:10, Pekka Savola a =E9crit :

> Note: the next rev of this doc (if there is one) should maybe be =20
> forwarded for comments on the ipv6-ops@lists.cluenet.de list.

will do.

>
> On Sat, 17 Sep 2005, Durand, Alain wrote:
>
>> How does this differ from RFC2772? Do you feel a need to update it?
>>
>
> RFC2772 includes guidelines for *6bone*.  This is offering =20
> guidelines for more than that.  In that light, if we feel the IETF =20
> is the right place to give guidance on this, updating is certainly =20
> needed.

see comment below.

>
> As already noted in the IETF/ipv6 lists, it's an open question to =20
> what degree and how strong guidance the IETF should (or even could) =20=

> give to the operators.
>
> It seems that if the IETF would want to pursue this work, the =20
> discussion would need to be recast in the manner "You should =20
> considering doing [this].  This is why it may or may not make =20
> sense". As we learned from the DNS configuration debates at DNSOP =20
> (though the situation is a bit difficult), getting to a consensus =20
> could be very difficult.
>
> A couple of specific comments:
>
>  - the global unicast address recommendations are (IMHO) way too =20
> lax. Even some part of 'strict' filters in http://www.space.net/=20
> ~gert/RIPE/ipv6-filters.html could be stricter. In any case, that =20
> URL should also be referred.  This is an example of the case why =20
> getting CONSENSUS on a document like this is going to be very =20
> difficult.

I knew that... ;-))

well. the intent here was to set the minimum (/48 or less) so that at =20=

least this is clear and I'm hoping there is a concensus on /48 or =20
less. In this case, the document with the other guidelines is useful =20
for operators.
for example, if the minimum is /48 or less, then we are filtering /=20
64! good progress!

By the time there is concensus on less than /48 (maybe after =20
multihoming work or ...), then we could revise it and make a new =20
version.

currently (to also respond to Alain comment on diff with RFC2772), =20
RFC2772 is the only "published" document I know that has some =20
guidelines on routing policies. and RFC2772 is outdated. So there is =20
a need for a document, with the minimum that has concensus to help =20
the ones who are deploying right now.

> Many folks don't see a problem w/ putting /48 junk etc. in the =20
> routing tables, others do.  This doc would/could then become a =20
> political battleground in the v6 operations community..

Why don't publish what is agreeable as a minimum and then revise it =20
when more experience/more concensus/other tools/... is in.

>
>  - the uppercase keywords are inappropriate and should be removed

you meant because it is not a protocol?

>
>  - the doc should probably make RFC2772 historic

I thought about that and I agree. I'm not sure when/how to put it. =20
Include in the document I guess?

Marc.


>
>
> --=20
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>





From owner-v6ops@ops.ietf.org Mon Sep 19 08:52:48 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EHL8a-000244-6V
	for v6ops-archive@megatron.ietf.org; Mon, 19 Sep 2005 08:52:48 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18820
	for <v6ops-archive@lists.ietf.org>; Mon, 19 Sep 2005 08:52:46 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EHL8O-000DU1-Lq
	for v6ops-data@psg.com; Mon, 19 Sep 2005 12:52:36 +0000
Received: from [209.71.226.4] (helo=ex.hexago.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.50 (FreeBSD))
	id 1EHL8N-000DTf-Tg
	for v6ops@ops.ietf.org; Mon, 19 Sep 2005 12:52:36 +0000
Received: from [209.71.226.82] (82.226.71.209.hexago.com [209.71.226.82] (may be forged))
	by ex.hexago.com ( hexago/8.13.4) with ESMTP id j8JCoxBd084085;
	Mon, 19 Sep 2005 08:50:59 -0400 (EDT)
	(envelope-from marc.blanchet@hexago.com)
In-Reply-To: <20050919083022.GH6059@login.ecs.soton.ac.uk>
References: <6EEEACD9D7F52940BEE26F5467C02C730DFA3E@PACDCEXCMB01.cable.comcast.com> <Pine.LNX.4.61.0509190859020.27448@netcore.fi> <20050919083022.GH6059@login.ecs.soton.ac.uk>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <70BEA888-608C-46B5-BD24-AD8C35DA465A@hexago.com>
Cc: v6ops@ops.ietf.org
Content-Transfer-Encoding: quoted-printable
From: Marc Blanchet <marc.blanchet@hexago.com>
Subject: Re: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt
Date: Mon, 19 Sep 2005 08:50:49 -0400
To: Chown Tim <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.734)
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


Le 05-09-19 =E0 04:30, Tim Chown a =E9crit :

> On Mon, Sep 19, 2005 at 09:10:01AM +0300, Pekka Savola wrote:
>
>>
>> RFC2772 includes guidelines for *6bone*.  This is offering guidelines
>> for more than that.  In that light, if we feel the IETF is the right
>> place to give guidance on this, updating is certainly needed.
>>
>
> Well yes, one recommendation is now on filtering 3ffe::/16 prefixes,
> at least from 06/06/06 ;)


well, I thought about it, but in fact, after 06/06/06, 3ffe::/16 =20
becomes like any non-allocated prefix.
So:
- before 06/0606, it is a valid prefix
- after 06/06/06,  it should be treated as any non-allocated prefix.

so, in fact, if you look at current text, it is already taken care =20
of... ;-))

>
>
>> As already noted in the IETF/ipv6 lists, it's an open question to =20
>> what
>> degree and how strong guidance the IETF should (or even could) =20
>> give to
>> the operators.
>>
>
> We have BCP in many areas.

you are right, the intented target level of the document was a BCP.


> As with everything else, nothing can be forced,
> so Bill can continue to do as he pleases.
>
>
>>  - the uppercase keywords are inappropriate and should be removed
>>
>
> I agree.  It is just guidelines.

ok.

Marc.

>
> --=20
> Tim/::1
>
>





From owner-v6ops@ops.ietf.org Tue Sep 20 00:55:24 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EHaA8-00046z-3e
	for v6ops-archive@megatron.ietf.org; Tue, 20 Sep 2005 00:55:24 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21601
	for <v6ops-archive@lists.ietf.org>; Tue, 20 Sep 2005 00:55:19 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EHa70-000Flh-3Q
	for v6ops-data@psg.com; Tue, 20 Sep 2005 04:52:10 +0000
Received: from [193.94.160.1] (helo=netcore.fi)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EHa6y-000Fl0-4I
	for v6ops@ops.ietf.org; Tue, 20 Sep 2005 04:52:08 +0000
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id j8K4ps520265;
	Tue, 20 Sep 2005 07:52:01 +0300
Date: Tue, 20 Sep 2005 07:51:54 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Marc Blanchet <marc.blanchet@hexago.com>
cc: "Durand, Alain" <Alain_Durand@cable.comcast.com>, v6ops@ops.ietf.org
Subject: Re: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt 
In-Reply-To: <339F3159-DCD2-4EA1-95D7-54836EC9AE1F@hexago.com>
Message-ID: <Pine.LNX.4.61.0509200747340.20145@netcore.fi>
References: <6EEEACD9D7F52940BEE26F5467C02C730DFA3E@PACDCEXCMB01.cable.comcast.com>
 <Pine.LNX.4.61.0509190859020.27448@netcore.fi> <339F3159-DCD2-4EA1-95D7-54836EC9AE1F@hexago.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

On Mon, 19 Sep 2005, Marc Blanchet wrote:
>> Many folks don't see a problem w/ putting /48 junk etc. in the routing 
>> tables, others do.  This doc would/could then become a political 
>> battleground in the v6 operations community..
>
> Why don't publish what is agreeable as a minimum and then revise it when more 
> experience/more concensus/other tools/... is in.

You mean, after the routing table has already been irreversibly 
polluted with junk, come back and review our past recommendations?

Sorry, I don't see how that could fly.  If we don't recommend (or at 
least describe the tradeoffs of) filtering at the allocation 
boundaries, we'd better not produce a document at all because the 
existance of such a document would be interpreted as the IETF's 
go-ahead for putting the junk in the routing tables.

>>  - the uppercase keywords are inappropriate and should be removed
>
> you meant because it is not a protocol?

Yes, and because this is not really an area where the IETF can make 
strict requirements like "must"..

>>  - the doc should probably make RFC2772 historic
>
> I thought about that and I agree. I'm not sure when/how to put it. Include in 
> the document I guess?

Yes, and if you're using XML2RFC, do something like:

<rfc ipr="full3978" category="info" 
docName="draft-blanchet-v6ops-routing-guidelines-01.txt" 
obsoletes="2772">

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From owner-v6ops@ops.ietf.org Tue Sep 20 06:47:24 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EHfej-00034W-RX
	for v6ops-archive@megatron.ietf.org; Tue, 20 Sep 2005 06:47:24 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21945
	for <v6ops-archive@lists.ietf.org>; Tue, 20 Sep 2005 06:47:18 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EHfc7-000FbI-I6
	for v6ops-data@psg.com; Tue, 20 Sep 2005 10:44:39 +0000
Received: from [209.71.226.4] (helo=ex.hexago.com)
	by psg.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.50 (FreeBSD))
	id 1EHfc6-000Fb5-Dh
	for v6ops@ops.ietf.org; Tue, 20 Sep 2005 10:44:38 +0000
Received: from [127.0.0.1] (retro.hexago.com [209.71.226.5])
	by ex.hexago.com ( hexago/8.13.4) with ESMTP id j8KAgtiF096474;
	Tue, 20 Sep 2005 06:42:56 -0400 (EDT)
	(envelope-from marc.blanchet@hexago.com)
In-Reply-To: <Pine.LNX.4.61.0509200747340.20145@netcore.fi>
References: <6EEEACD9D7F52940BEE26F5467C02C730DFA3E@PACDCEXCMB01.cable.comcast.com> <Pine.LNX.4.61.0509190859020.27448@netcore.fi> <339F3159-DCD2-4EA1-95D7-54836EC9AE1F@hexago.com> <Pine.LNX.4.61.0509200747340.20145@netcore.fi>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <19D3671D-EEF8-47CD-BC0B-D3F2FA136527@hexago.com>
Cc: "Durand, Alain" <Alain_Durand@cable.comcast.com>, v6ops@ops.ietf.org
Content-Transfer-Encoding: quoted-printable
From: Marc Blanchet <marc.blanchet@hexago.com>
Subject: Re: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt 
Date: Tue, 20 Sep 2005 06:42:43 -0400
To: Pekka Savola <pekkas@netcore.fi>
X-Mailer: Apple Mail (2.734)
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable


Le 05-09-20 =E0 00:51, Pekka Savola a =E9crit :

> On Mon, 19 Sep 2005, Marc Blanchet wrote:
>
>>> Many folks don't see a problem w/ putting /48 junk etc. in the =20
>>> routing tables, others do.  This doc would/could then become a =20
>>> political battleground in the v6 operations community..
>>>
>>
>> Why don't publish what is agreeable as a minimum and then revise =20
>> it when more experience/more concensus/other tools/... is in.
>>
>
> You mean, after the routing table has already been irreversibly =20
> polluted with junk, come back and review our past recommendations?

- no. you are missing the point.

- currently no recommendation. so /128 can fly.
- what is the number then, if not /48? I'm fine with better than /48, =20=

but I thought that concensus will be difficult with a number less =20
than /48.
- and if you read the text, /48 is the minimum.
- maybe you can provide some text?

>
> Sorry, I don't see how that could fly.  If we don't recommend (or =20
> at least describe the tradeoffs of) filtering at the allocation =20
> boundaries, we'd better not produce a document at all because the =20
> existance of such a document would be interpreted as the IETF's go-=20
> ahead for putting the junk in the routing tables.

so you are proposing /32?  Can you provide text?

>
>
>>>  - the uppercase keywords are inappropriate and should be removed
>>>
>>
>> you meant because it is not a protocol?
>>
>
> Yes, and because this is not really an area where the IETF can make =20=

> strict requirements like "must"..

will do.

>
>
>>>  - the doc should probably make RFC2772 historic
>>>
>>
>> I thought about that and I agree. I'm not sure when/how to put it. =20=

>> Include in the document I guess?
>>
>
> Yes, and if you're using XML2RFC, do something like:
>
> <rfc ipr=3D"full3978" category=3D"info" docName=3D"draft-blanchet-v6ops-=
=20
> routing-guidelines-01.txt" obsoletes=3D"2772">

yeap, you guess it.

Marc.


>
> --=20
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>





From owner-v6ops@ops.ietf.org Wed Sep 21 06:29:04 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EI1qZ-0001hN-VP
	for v6ops-archive@megatron.ietf.org; Wed, 21 Sep 2005 06:29:04 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10320
	for <v6ops-archive@lists.ietf.org>; Wed, 21 Sep 2005 06:29:01 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EI1nZ-000Gyp-4d
	for v6ops-data@psg.com; Wed, 21 Sep 2005 10:25:57 +0000
Received: from [193.94.160.1] (helo=netcore.fi)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EI1nV-000GyS-UV
	for v6ops@ops.ietf.org; Wed, 21 Sep 2005 10:25:54 +0000
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id j8LAPdc21291;
	Wed, 21 Sep 2005 13:25:40 +0300
Date: Wed, 21 Sep 2005 13:25:39 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Marc Blanchet <marc.blanchet@hexago.com>
cc: "Durand, Alain" <Alain_Durand@cable.comcast.com>, v6ops@ops.ietf.org
Subject: Re: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt 
In-Reply-To: <19D3671D-EEF8-47CD-BC0B-D3F2FA136527@hexago.com>
Message-ID: <Pine.LNX.4.61.0509211305280.20876@netcore.fi>
References: <6EEEACD9D7F52940BEE26F5467C02C730DFA3E@PACDCEXCMB01.cable.comcast.com>
 <Pine.LNX.4.61.0509190859020.27448@netcore.fi> <339F3159-DCD2-4EA1-95D7-54836EC9AE1F@hexago.com>
 <Pine.LNX.4.61.0509200747340.20145@netcore.fi> <19D3671D-EEF8-47CD-BC0B-D3F2FA136527@hexago.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

On Tue, 20 Sep 2005, Marc Blanchet wrote:
>> You mean, after the routing table has already been irreversibly polluted 
>> with junk, come back and review our past recommendations?
>
> - no. you are missing the point.
>
> - currently no recommendation. so /128 can fly.
> - what is the number then, if not /48? I'm fine with better than /48, but I 
> thought that concensus will be difficult with a number less than /48.
> - and if you read the text, /48 is the minimum.
> - maybe you can provide some text?

No.  If there is no appropriate IETF statement on this, the folks 
probably think the IETF hasn't made a firm opinion on this, and seek 
guidance from elsewhere.  Many use strict filters, others relaxed, 
some may not filter at all.  That is, the lack of IETF guidance on 
filtering doesn't mean the operators can't (and don't) filter -- 
operators seem to be capable of publishing some filtering suggestions 
on their own (e.g., Gert's web page).

So, any guidance the IETF makes must be good, not simply "anything is 
better than nothing".

>> Sorry, I don't see how that could fly.  If we don't recommend (or at least 
>> describe the tradeoffs of) filtering at the allocation boundaries, we'd 
>> better not produce a document at all because the existance of such a 
>> document would be interpreted as the IETF's go-ahead for putting the junk 
>> in the routing tables.
>
> so you are proposing /32?  Can you provide text?

Ok, here's something to demonstrate a different starting point.

3.5.  Global Unicast

    The global unicast routes (2000::/3) [RFC3513] may be advertised in an
    IGP or EGP.

3.5.1 Filtering on Allocation Boundaries

   In IPv4 as of 2005, over 50% of routing table entries are used by
   more-specific route advertisements [http://bgp.potaroo.net].  These are
   a result of a number of sources such as misconfigurations, traffic
   engineering, multihoming, switching providers without renumbering,
   etc.

   From the larger perspective, however, these are more or less
   unnecessary "junk".  In 6bone, prefix filters to weed out
   more specifics were required [RFC2772] to weed out such routes.
   This is also a valid practise for production networks as
   it will help in keeping the routing table compact and clean;
   the cleaner the global routing table is, the more difficult it
   is for people to start polluting it.

   Therefore, filtering based on the allocation boundaries is
   recommended.  For the sake of simplicity (as the allocation
   boundaries have varied mainly between /19 and /32), the
   policy could be to allow advertisements up to /32, and /35
   for older allocations in 2001::/16, and the more specifics only
   by exception.  One particular exception to keep in mind in
   particular is ARIN's critical internet infrastructure
   micro-allocation block (2001:500::/32) where up to /48's
   should be allowed.

....

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings




From owner-v6ops@ops.ietf.org Fri Sep 23 12:07:39 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIq5K-0000wl-TQ
	for v6ops-archive@megatron.ietf.org; Fri, 23 Sep 2005 12:07:38 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22898
	for <v6ops-archive@lists.ietf.org>; Fri, 23 Sep 2005 12:07:36 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EIq2a-0000CL-NJ
	for v6ops-data@psg.com; Fri, 23 Sep 2005 16:04:48 +0000
Received: from [130.76.96.56] (helo=stl-smtpout-01.boeing.com)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EIq2Y-0000Bz-Nt
	for v6ops@ops.ietf.org; Fri, 23 Sep 2005 16:04:46 +0000
Received: from blv-av-01.boeing.com ([192.42.227.216])
	by stl-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id LAA05253;
	Fri, 23 Sep 2005 11:04:45 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id j8NG4jp00266;
	Fri, 23 Sep 2005 09:04:45 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 23 Sep 2005 09:04:44 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Link Adaptation for IPv6-in-IPv4 Tunnels 
Date: Fri, 23 Sep 2005 09:04:43 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10D5049@XCH-NW-7V2.nw.nos.boeing.com>
Thread-Topic: Link Adaptation for IPv6-in-IPv4 Tunnels 
Thread-Index: AcWuf9vujek7NJxqQFmjIkAgvtzOGgR0+O3Q
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Fred Baker" <fred@cisco.com>
Cc: <v6ops@ops.ietf.org>
X-OriginalArrivalTime: 23 Sep 2005 16:04:44.0070 (UTC) FILETIME=[83326460:01C5C058]
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hello Fred,

A while back, we had an exchange on the v6ops list regarding
a proposal for doing link adaptation over IPv6-in-IPv4 tunnels.
Your comments pointed out a glaring error that is (hopefully)
fixed now. See:

 http://www.ietf.org/internet-drafts/draft-templin-linkadapt-01.txt

Although the gist of the ensuing discussion was that the
document could not be worked out of v6ops since it proposes
a new mechanism/protocol, one angle we did not explore was
whether it could be contributed as an extension to an
*existing* v6ops work item.

In particular, what the link adapation work proposes could
make for a natural extension to "Basic Transition Mechanisms"
(i.e., draft-ietf-v6ops-mech-v2-07) and would in fact complete
that work in such a way that other transition mechanisms that
cite [MECH] can also take advantage of the larger MTUs.

Can this work be contributed as an extension to [MECH]?

Fred
fred.l.templin@boeing.com =20

> -----Original Message-----
> From: Fred Baker [mailto:fred@cisco.com]=20
> Sent: Wednesday, August 31, 2005 4:01 PM
> To: Templin, Fred L
> Cc: Lindqvist Erik Kurt; v6ops@ops.ietf.org
> Subject: Re: RE:=20
>=20
> no, it doesn't, for two reasons.
>=20
> First, in a best effort network, it is invalid to presume that order =20
> will be preserved in the network.
>=20
> Second, changing the identifier field in IPv4 from 16 bits to 10 and =20
> using the remaining bits to indicate something else is a change to =20
> the identifier field in IPv4. RFC 791 and RFC 1122 merely specify =20
> that the identifiers should be locally unique within a field=20
> of time, =20
> not that they have certain characteristics from which other =20
> functionality may be deduced.
>=20
> I really not trying to be a pain here, but you really need to take =20
> this to a working group that does protocols, and specifically=20
> in this =20
> case, does changes to IPv4. v6ops can develop requirements=20
> for such a =20
> protocol if you like, but the protocol work needs to be done =20
> somewhere appropriate to the protocol.
>=20
> On Aug 31, 2005, at 3:29 PM, Templin, Fred L wrote:
>=20
> > Fred,
> >
> > What I suggested in my previous message was more dramatic
> > (and complicated) than what is really needed. If the tunnel
> > encapsulator simply defines for itself a coding for the
> > 16-bit IPv4 Identification field such as the following:
> >
> >     0                   1
> >     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |  Identification   |A|Segment #|
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> > then the requirements of RFC 791 (and the others) are observed
> > and there is no change to IPv4.
> >
> > The bits encoded in the field would include a 10-bit ID, a
> > 1-bit Auxilliary fragmentation flag and a 5-bit Segment number
> > for use by the tunnel decapsulator to reassemble a packet that
> > was segmented according to the link adaptation spec. There is
> > no need for a "Type-2 IPv4 fragmentation", there is no need to
> > set the Reserved fragmentation bit and there is no interaction
> > with ordinary IPv4 fragmentation/reassembly regardless of the
> > setting of the DF bit.
> >
> > All that is needed is for the decapsulator to have a means for
> > receiving the 16-bit Identification field intact following IPv4
> > reassembly and a means for the encapsulator to discover whether
> > the decapsulator implements the link adaptation scheme.
> >
> > One concern is that the actual Identifier is shrunk down to
> > 10 bits instead of 16, meaning that the degree of packet
> > reordering in the network should be such that packets are
> > rarely mis-ordered by more than 1024 places. This is part of
> > the motivation for using a checksum to detect packet splicing
> > errors such as suggested by the link adapatation document.
> >
> > Does this help address your concerns regarding changes to IPv4
> > and defining new protocols?
> >
> > Fred
> > fred.l.templin@boeing.com
> >
> >
> >> -----Original Message-----
> >> From: Fred Baker [mailto:fred@cisco.com]
> >> Sent: Tuesday, August 30, 2005 3:18 PM
> >> To: Templin, Fred L
> >> Cc: Lindqvist Erik Kurt; v6ops@ops.ietf.org
> >> Subject: Re:
> >>
> >> On Aug 29, 2005, at 7:30 PM, Templin, Fred L wrote:
> >>
> >>> So, can we call this a new (extension, mechanism, method, etc.)
> >>> instead of a new protocol and run it past the v6ops charter again?
> >>>
> >>
> >> If it uses IPv4 fields but re-interprets them in a way that
> >> RFCs 791,
> >> 1122/3, 1812, 1349, and 2474 don't discuss, it is a change to
> >> IPv4. I
> >> would suggest discussing it in a working group that suggests
> >> modifications to IPv4. If it's implemented in a header outside of
> >> IPv4, it's a new protocol, and needs to be discussed in a WG that
> >> deals with that.
> >>
> >
>=20




From owner-v6ops@ops.ietf.org Fri Sep 23 12:25:53 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIqMz-0006qZ-8e
	for v6ops-archive@megatron.ietf.org; Fri, 23 Sep 2005 12:25:53 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23758
	for <v6ops-archive@lists.ietf.org>; Fri, 23 Sep 2005 12:25:50 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EIqME-0002um-Pv
	for v6ops-data@psg.com; Fri, 23 Sep 2005 16:25:06 +0000
Received: from [171.68.10.87] (helo=sj-iport-5.cisco.com)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EIqMD-0002uZ-3W
	for v6ops@ops.ietf.org; Fri, 23 Sep 2005 16:25:05 +0000
Received: from sj-core-3.cisco.com ([171.68.223.137])
  by sj-iport-5.cisco.com with ESMTP; 23 Sep 2005 09:24:13 -0700
X-IronPort-AV: i="3.97,141,1125903600"; 
   d="scan'208"; a="214415104:sNHT1769511542"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j8NGO4Vt018652;
	Fri, 23 Sep 2005 09:24:04 -0700 (PDT)
Received: from [10.32.244.218] (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id j8NGaCYZ022612;
	Fri, 23 Sep 2005 09:36:12 -0700
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A10D5049@XCH-NW-7V2.nw.nos.boeing.com>
References: <39C363776A4E8C4A94691D2BD9D1C9A10D5049@XCH-NW-7V2.nw.nos.boeing.com>
Mime-Version: 1.0 (Apple Message framework v734)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BA5D6757-510D-409E-AA40-1F852A347413@cisco.com>
Cc: <v6ops@ops.ietf.org>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: Link Adaptation for IPv6-in-IPv4 Tunnels 
Date: Fri, 23 Sep 2005 09:24:09 -0700
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.734)
DKIM-Signature: a=rsa-sha1;  q=dns; l=645; t=1127493372; x=1127925572;
	c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding;
	d=cisco.com; i=fred@cisco.com; 
	z=Subject:Re=3A=20Link=20Adaptation=20for=20IPv6-in-IPv4=20Tunnels=20|
	From:Fred=20Baker=20<fred@cisco.com>|
	Date:Fri,=2023=20Sep=202005=2009=3A24=3A09=20-0700|
	Content-Type:text/plain=3B=20charset=3DUS-ASCII=3B=20delsp=3Dyes=3B=20format=3Dflowed|
	Content-Transfer-Encoding:7bit;
	b=MyU7JA35XthJnChJWEx2ytm9RJ+AraT7kG6Xf0SWMYOhGWOG49x9NHxhAdemDxoogy+LX7Hq
	junJdJefsaruVw6sWeEegoULQhAjMVBKjYphT8+zgQG/fQ4WC10sitexpm7eToP47IdfJ5Za6Ml
	8+KrFn+9h9HsJqI1IuUx4wXc=
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com; dkim=pass (
	message from cisco.com verified; ); 
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Does it still propose a protocol or protocol change?

I don't know offhand whether the charter of v6ops then precluded  
protocol work, and won't go into whether it was proper for [MECH] to  
be done in v6ops. Given the present charter, I can treat it as a  
requirements document that may be asking for something like the work  
you are proposing. But my read of the document you pointed to is that  
it is still proposing an incompatible change (as in "unchanged  
equipment will not perform the function and once the message is  
segmented in this fashion it must be reassembled in this fashion.

I think that has to be done in a WG chartered to do non-backward- 
compatible changes to IPv4.

On Sep 23, 2005, at 9:04 AM, Templin, Fred L wrote:

> Can this work be contributed as an extension to [MECH]?
>




From owner-v6ops@ops.ietf.org Fri Sep 23 12:37:37 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIqYL-0001BB-0i
	for v6ops-archive@megatron.ietf.org; Fri, 23 Sep 2005 12:37:37 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24244
	for <v6ops-archive@lists.ietf.org>; Fri, 23 Sep 2005 12:37:34 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EIqXj-0004Hi-9T
	for v6ops-data@psg.com; Fri, 23 Sep 2005 16:36:59 +0000
Received: from [130.76.64.48] (helo=slb-smtpout-01.boeing.com)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EIqXh-0004HR-98
	for v6ops@ops.ietf.org; Fri, 23 Sep 2005 16:36:57 +0000
Received: from blv-av-01.boeing.com ([192.42.227.216])
	by slb-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id JAA08613;
	Fri, 23 Sep 2005 09:36:56 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id j8NGaup03204;
	Fri, 23 Sep 2005 09:36:56 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 23 Sep 2005 09:36:56 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Link Adaptation for IPv6-in-IPv4 Tunnels 
Date: Fri, 23 Sep 2005 09:36:55 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10D504A@XCH-NW-7V2.nw.nos.boeing.com>
Thread-Topic: Link Adaptation for IPv6-in-IPv4 Tunnels 
Thread-Index: AcXAW1x+TtPa9HKuRSa+/F0sREjUuQAACbWQ
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Fred Baker" <fred@cisco.com>
Cc: <v6ops@ops.ietf.org>
X-OriginalArrivalTime: 23 Sep 2005 16:36:56.0233 (UTC) FILETIME=[02DB1190:01C5C05D]
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Fred,

One additional point is that there is built-in support for backwards
compatibility. There is a means for the tunnel encapsulator to learn
whether the decapsulator implements the new method (and revert to the
old method otherwise) and a means for the decapsulator to learn whether
the encapsulator implements the new method (again, reverting to the
old method otherwise).

But my intention in bringing this up is simply to explore the [MECH]
angle; not to dogmatically push for v6ops adoption.

Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Fred Baker [mailto:fred@cisco.com]=20
> Sent: Friday, September 23, 2005 9:24 AM
> To: Templin, Fred L
> Cc: v6ops@ops.ietf.org
> Subject: Re: Link Adaptation for IPv6-in-IPv4 Tunnels=20
>=20
> Does it still propose a protocol or protocol change?
>=20
> I don't know offhand whether the charter of v6ops then precluded =20
> protocol work, and won't go into whether it was proper for [MECH] to =20
> be done in v6ops. Given the present charter, I can treat it as a =20
> requirements document that may be asking for something like the work =20
> you are proposing. But my read of the document you pointed to=20
> is that =20
> it is still proposing an incompatible change (as in "unchanged =20
> equipment will not perform the function and once the message is =20
> segmented in this fashion it must be reassembled in this fashion.
>=20
> I think that has to be done in a WG chartered to do non-backward-=20
> compatible changes to IPv4.
>=20
> On Sep 23, 2005, at 9:04 AM, Templin, Fred L wrote:
>=20
> > Can this work be contributed as an extension to [MECH]?
> >
>=20




From owner-v6ops@ops.ietf.org Fri Sep 23 14:03:40 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIrtc-0004st-1M
	for v6ops-archive@megatron.ietf.org; Fri, 23 Sep 2005 14:03:40 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27749
	for <v6ops-archive@lists.ietf.org>; Fri, 23 Sep 2005 14:03:38 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EIrrq-000F3E-3c
	for v6ops-data@psg.com; Fri, 23 Sep 2005 18:01:50 +0000
Received: from [205.167.76.9] (helo=m106.maoz.com)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EIrrn-000F2o-Dr
	for v6ops@ops.ietf.org; Fri, 23 Sep 2005 18:01:47 +0000
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.13.4/8.13.4) with ESMTP id j8NI1iJA021857;
	Fri, 23 Sep 2005 11:01:44 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.13.4/8.12.11/Submit) id j8NI1iJV021856;
	Fri, 23 Sep 2005 11:01:44 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Fri, 23 Sep 2005 11:01:44 -0700
From: David Meyer <dmm@1-4-5.net>
To: v6ops@ops.ietf.org
Cc: fred@cisco.com, kurtis@kurtis.pp.se
Subject: IPv6 Multi-homing BOF at NANOG 35
Message-ID: <20050923180144.GA21702@1-4-5.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP"
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I find your lack of faith disturbing." -- Darth Vader, Star Wars Episode IV.
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk


--jRHKVT23PllUwdXP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


	Folks,

	The IAB has proposed the below BOF for the upcoming NANOG
	(please see http://www.nanog.org for information on
	NANOG). As mentioned in the description (see below), the
	purpose of the BOF is for the IAB to solicit operator
	feedback on the progress and direction of IETF IPv6
	multi-homing work, and to help the IAB determine if there
	is meaningful work that it can do (or can signal to the
	appropriate IETF working group(s)) to address any issues
	that may be perceived with the current direction.     =20

	Please let us know if you have any questions or comments,
	and watch the NANOG pages in the upcoming days for the
	NANOG agenda.=20

	Thanks, and hope to see you there.

	Dave (for the IAB)

=09
--

IAB IPv6 Multi-Homing BOF


With the advent of the growing and wide-spread deployment of
IPv6, many familiar operational issues have arisen. Among the
current IPv6 "hot topics" are RIR policy (including the HD ratio
discussion) and site multi-homing. This BOF proposal focuses on
the multi-homing issue, since multi-homing is one of the
significant drivers of the growth and dynamic properties of
Default Free Zone (DFZ). In particular, there is concern that
that the amount of multi-homing will grow beyond the
organizations who use it today in the IPv4 Internet and that=20
new mechanisms will be required to to handle that growth.=20

The current direction that the IETF is taking is being defined by
the shim6 working group. Briefly, shim6 seeks to find a mechanism
which provides most of the functional benefits of multi-homing while
still allowing reasonable scalability of the DFZ. Note that=20
multi-homing under shim6 differs from multi-homing under IPv4
since in IPv4 case, multi-homing is accomplished (in most cases)
by injecting a provider-independent (PI) prefix into the DFZ.
This approach has the property that it scales in the number of
multi-homed sites; each multi-homed site requires an unique entry
in the DFZ. shim6 differs from the IPv4 approach in that it does
not require an entry in the DFZ per multi-homed site.=20

The purpose of this BOF for the IAB is to solicit operator
feedback on the progress and direction of IPv6 multi-homing work,
particularly as discussed in the IETF, and to help the IAB
determine if there is meaningful work that it can do or can
signal to the appropriate IETF WGs to address any problem(s) that
may be perceived with the current direction.   Minimally, notes
of the session will be posted for those unable to attend the
discussion in person.




--jRHKVT23PllUwdXP
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFDNEMIORgD1qCZ2KcRAv6BAJ0SHwOZQxypi+mMKDB4K6gJ5biLDQCeJQ1k
nr3dIoLwRf+l5fxOlmtuLIY=
=MPBb
-----END PGP SIGNATURE-----

--jRHKVT23PllUwdXP--




From owner-v6ops@ops.ietf.org Fri Sep 23 17:42:04 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIvIy-0000UE-0x
	for v6ops-archive@megatron.ietf.org; Fri, 23 Sep 2005 17:42:04 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16616
	for <v6ops-archive@lists.ietf.org>; Fri, 23 Sep 2005 17:42:01 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EIvGK-000FMn-9i
	for v6ops-data@psg.com; Fri, 23 Sep 2005 21:39:20 +0000
Received: from [131.228.20.96] (helo=mgw-ext04.nokia.com)
	by psg.com with esmtps (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.50 (FreeBSD))
	id 1EIvGJ-000FMY-3o
	for v6ops@ops.ietf.org; Fri, 23 Sep 2005 21:39:19 +0000
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j8NLb3CH029995;
	Sat, 24 Sep 2005 00:37:07 +0300
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Sat, 24 Sep 2005 00:39:13 +0300
Received: from dadhcp-172019068136.americas.nokia.com ([10.241.59.110]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881);
	 Sat, 24 Sep 2005 00:39:12 +0300
Received: from dadhcp-172019068136.americas.nokia.com (localhost.localdomain [127.0.0.1])
	by dadhcp-172019068136.americas.nokia.com (8.12.11/8.12.11) with ESMTP id j8NLdOe5004846;
	Fri, 23 Sep 2005 14:39:24 -0700
Received: (from david@localhost)
	by dadhcp-172019068136.americas.nokia.com (8.12.11/8.12.11/Submit) id j8NLdNmT004845;
	Fri, 23 Sep 2005 14:39:23 -0700
Date: Fri, 23 Sep 2005 14:39:22 -0700
From: David Kessens <david.kessens@nokia.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Cc: v6ops@ops.ietf.org
Subject: Re: Link Adaptation for IPv6-in-IPv4 Tunnels
Message-ID: <20050923213922.GB4703@nokia.com>
References: <39C363776A4E8C4A94691D2BD9D1C9A10D504A@XCH-NW-7V2.nw.nos.boeing.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A10D504A@XCH-NW-7V2.nw.nos.boeing.com>
User-Agent: Mutt/1.4.1i
X-OriginalArrivalTime: 23 Sep 2005 21:39:13.0619 (UTC) FILETIME=[3D948A30:01C5C087]
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk


Fred,

On Fri, Sep 23, 2005 at 09:36:55AM -0700, Templin, Fred L wrote:
> 
> But my intention in bringing this up is simply to explore the [MECH]
> angle; not to dogmatically push for v6ops adoption.

It doesn't matter how you name it, but no matter how you look at it
you are trying to push something that is out of charter for v6ops.

David Kessens
---




From owner-v6ops@ops.ietf.org Fri Sep 23 20:54:09 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIyIp-0002Zl-UM
	for v6ops-archive@megatron.ietf.org; Fri, 23 Sep 2005 20:54:09 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25543
	for <v6ops-archive@lists.ietf.org>; Fri, 23 Sep 2005 20:54:06 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EIyEA-000CHI-AR
	for v6ops-data@psg.com; Sat, 24 Sep 2005 00:49:18 +0000
Received: from [171.71.176.72] (helo=sj-iport-3.cisco.com)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EIyE7-000CGy-Ft
	for v6ops@ops.ietf.org; Sat, 24 Sep 2005 00:49:15 +0000
Received: from sj-core-1.cisco.com ([171.71.177.237])
  by sj-iport-3.cisco.com with ESMTP; 23 Sep 2005 17:49:15 -0700
X-IronPort-AV: i="3.97,142,1125903600"; 
   d="scan'208"; a="345050840:sNHT29038520"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j8O0nD4u013446
	for <v6ops@ops.ietf.org>; Fri, 23 Sep 2005 17:49:13 -0700 (PDT)
Received: from [10.32.244.218] (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id j8O113SH026937
	for <v6ops@ops.ietf.org>; Fri, 23 Sep 2005 18:01:13 -0700
Mime-Version: 1.0 (Apple Message framework v734)
References: <E1EIejC-0003qn-31@newodin.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C7D91F17-BACD-4861-B259-D0E99BD110DC@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Fwd: Approval to Post Version -00 Internet-Drafts for the 64th IETF Meeting in Vancouver, British Columbia, Canada 
Date: Fri, 23 Sep 2005 17:49:12 -0700
To: v6ops@ops.ietf.org
X-Mailer: Apple Mail (2.734)
DKIM-Signature: a=rsa-sha1;  q=dns; l=1164; t=1127523673; x=1127955873;
	c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding;
	d=cisco.com; i=fred@cisco.com; 
	z=Subject:Fwd=3A=20Approval=20to=20Post=20Version=20-00=20Internet-Drafts=20for=20
	the=2064th=20IETF=20Meeting=20in=20Vancouver,=20British=20Columbia,=20Canad
	a=20|
	From:Fred=20Baker=20<fred@cisco.com>|
	Date:Fri,=2023=20Sep=202005=2017=3A49=3A12=20-0700|
	Content-Type:text/plain=3B=20charset=3DUS-ASCII=3B=20delsp=3Dyes=3B=20format=3Dflowed|
	Content-Transfer-Encoding:7bit;
	b=pbv2gj6b+mVJaRd9Do9ENcDmMRvUAiLIxCPRTByF6+iz1ZePeFBkbSLun1EhC3L9JLH3NsHn
	9+VgNRJ934gZXX4MJLJu4BrQPQI1ClXHTDbugDD32jNosrWgMwkCs0PVrUkhsTocI8mRX6N0ZxI
	PnmrXlbG9/Cv1hL2bYMJKlk4=
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com; dkim=pass (
	message from cisco.com verified; ); 
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Begin forwarded message:

> From: Internet-Drafts Administrator <internet-drafts@ietf.org>
> Date: September 22, 2005 9:00:02 PM PDT
> To: Working Group Chairs <wgchairs@ietf.org>
> Subject: Approval to Post Version -00 Internet-Drafts for the 64th  
> IETF Meeting in Vancouver, British Columbia, Canada
>
>
>
> Dear IETF Working Group Chairs:
>
> In order to expedite the processing of the many version -00 I-Ds that
> the Secretariat receives before an IETF meeting, we ask that you
> please notify the Secretariat prior to the initial submission cutoff
> date of all version -00 I-Ds that you expect to approve for posting as
> WG documents.  Please send the filenames of your approved -00 I-Ds to
> internet-drafts@ietf.org.  We would appreciate receiving your list of
> approved drafts five (5) business days prior to the cutoff date for  
> -00
> submissions, or by Monday, October 10th at 9:00 AM ET for the 64th  
> IETF
> Meeting.  Please include the word "Approved I-Ds" in the "Subject"
> field.  This procedure will help to ensure that version -00 I-Ds are
> posted in a timely manner, allowing more time for review by the  
> public.
>
> Thank you for your cooperation in this matter.
>
> The Internet-Drafts Administrator
>
> FYI: The Internet-Draft cutoff dates as well as other significant  
> dates
> for the 64th IETF Meeting can be found at http://www.ietf.org/ 
> meetings/cutoff_dates_64.html.
>




From owner-v6ops@ops.ietf.org Fri Sep 23 20:54:14 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EIyIw-0002a3-FN
	for v6ops-archive@megatron.ietf.org; Fri, 23 Sep 2005 20:54:14 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA25553
	for <v6ops-archive@lists.ietf.org>; Fri, 23 Sep 2005 20:54:12 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.50 (FreeBSD))
	id 1EIyDz-000CGX-22
	for v6ops-data@psg.com; Sat, 24 Sep 2005 00:49:07 +0000
Received: from [171.71.176.70] (helo=sj-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.50 (FreeBSD))
	id 1EIyDx-000CGI-RH
	for v6ops@ops.ietf.org; Sat, 24 Sep 2005 00:49:05 +0000
Received: from sj-core-5.cisco.com ([171.71.177.238])
  by sj-iport-1.cisco.com with ESMTP; 23 Sep 2005 17:49:05 -0700
X-IronPort-AV: i="3.97,142,1125903600"; 
   d="scan'208"; a="661768065:sNHT30063228"
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j8O0n34V009004
	for <v6ops@ops.ietf.org>; Fri, 23 Sep 2005 17:49:03 -0700 (PDT)
Received: from [10.32.244.218] (stealth-10-32-244-218.cisco.com [10.32.244.218])
	by imail.cisco.com (8.12.11/8.12.10) with SMTP id j8O113SG026937
	for <v6ops@ops.ietf.org>; Fri, 23 Sep 2005 18:01:03 -0700
Mime-Version: 1.0 (Apple Message framework v734)
References: <E1EG7OL-0001k5-9J@newodin.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6D6AF520-5B50-4AB7-8A80-C8BFFE34E4DE@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Fwd: Internet-Drafts Submission Cutoff Dates for the 64th IETF Meeting in Vancouver, British Columbia, Canada 
Date: Fri, 23 Sep 2005 17:49:01 -0700
To: v6ops@ops.ietf.org
X-Mailer: Apple Mail (2.734)
DKIM-Signature: a=rsa-sha1;  q=dns; l=1830; t=1127523663; x=1127955863;
	c=nowsp; s=nebraska; h=Subject:From:Date:Content-Type:Content-Transfer-Encoding;
	d=cisco.com; i=fred@cisco.com; 
	z=Subject:Fwd=3A=20Internet-Drafts=20Submission=20Cutoff=20Dates=20for=20the=2064t
	h=20IETF=20Meeting=20in=20Vancouver,=20British=20Columbia,=20Canada=20|
	From:Fred=20Baker=20<fred@cisco.com>|
	Date:Fri,=2023=20Sep=202005=2017=3A49=3A01=20-0700|
	Content-Type:text/plain=3B=20charset=3DUS-ASCII=3B=20delsp=3Dyes=3B=20format=3Dflowed|
	Content-Transfer-Encoding:7bit;
	b=j3k6g1Znp+q8bfMpfuEgvppRT2k2EvLUjXu/JttT6ZvM2Nrowb887PIsWx3zPdI3ZBOrFr0p
	WEgpPdtcajT3E60dyHc3JTcycH6ZA0IQUGMpl29/YcCDsWMa1I2dxqU4RTDzKeZqIUG1huKeFiG
	U1HBBH8KLHhrg2tWen6SbJrw=
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com; dkim=pass (
	message from cisco.com verified; ); 
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Begin forwarded message:

> From: ietf-secretariat@ietf.org
> Date: September 15, 2005 9:00:01 PM PDT
> To: ietf-announce@ietf.org
> Subject: Internet-Drafts Submission Cutoff Dates for the 64th IETF  
> Meeting in Vancouver, British Columbia, Canada
>
>
>
> There are two (2) Internet-Draft cutoff dates for the 64th
> IETF Meeting in Vancouver, British Columbia, Canada:
>
> October 17th: Cutoff Date for Initial (i.e., version -00)
> Internet-Draft Submissions
>
> All initial Internet-Drafts (version -00) must be submitted by Monday,
> October 17th at 9:00 AM ET. As always, all initial submissions with a
> filename beginning with "draft-ietf" must be approved by the
> appropriate WG Chair before they can be processed or announced.  The
> Secretariat would appreciate receiving WG Chair approval by Monday,
> October 10th at 9:00 AM ET.
>
> October 24th: Cutoff Date for Revised (i.e., version -01 and higher)
> Internet-Draft Submissions
>
> All revised Internet-Drafts (version -01 and higher) must be submitted
> by Monday, October 24th at 9:00 AM ET.
>
> Initial and revised Internet-Drafts received after their respective
> cutoff dates will not be made available in the Internet-Drafts
> directory or announced until on or after Monday, November 7th at 9:00
> AM ET, when Internet-Draft posting resumes.  Please do not wait until
> the last minute to submit.
>
> PLEASE NOTE THE CHANGE OF PROCEDURE:  If you submit an initial or
> revised Internet-Draft after their respective cutoff deadlines, then
> your document will be retained and posted when Internet-Draft
> processing resumes.  You will no longer be required to resubmit the
> document.
>
> Thank you for your understanding and cooperation. If you have any
> questions or concerns, then please send a message to
> internet-drafts@ietf.org.
>
> The IETF Secretariat
>
> FYI: The Internet-Draft cutoff dates as well as other significant  
> dates
> for the 64th IETF Meeting can be found at http://www.ietf.org/ 
> meetings/cutoff_dates_64.html.
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
>




From Varnahov@8848.net Sun Sep 25 05:06:02 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EJSSP-00016A-MV
	for v6ops-archive@megatron.ietf.org; Sun, 25 Sep 2005 05:06:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00876
	for <v6ops-archive@ietf.org>; Sun, 25 Sep 2005 05:05:48 -0400 (EDT)
Received: from s01060050bf91fbaa.wp.shawcable.net ([24.77.195.250] helo=world4fun.ch)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1EJSZ2-0000MF-E7
	for v6ops-archive@ietf.org; Sun, 25 Sep 2005 05:12:54 -0400
From: "Paiva Leandra" <Varnahov@8848.net>
To: "Ghircoias Alan" <v6ops-archive@ietf.org>
Subject: Re[2]:
Date: Sun, 25 Sep 2005 09:05:48 +0000
X-SA-Do-Not-Rej: Yes
Message-ID: <0db501c5c1b0$29f68290$9cffac2f@world4fun.ch>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_7A89_B53D40CE.1F627A89"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1441
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Spam-Score: 4.1 (++++)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2

This is a multi-part message in MIME format.

------=_NextPart_000_7A89_B53D40CE.1F627A89
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Let there be sex!

SPUR-m [Sperm pills]: http://giddies.com/

------=_NextPart_000_7A89_B53D40CE.1F627A89
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
Let there be sex!
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>SPUR-m [Sperm pills]: <A=20
href=3D"http://giddies.com/">http://giddies.com/</A></FONT></DIV>
</BODY></HTML>

------=_NextPart_000_7A89_B53D40CE.1F627A89--




From Henrique@tvnet.lv Sun Sep 25 07:22:14 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EJUaE-0003oU-0N
	for v6ops-archive@megatron.ietf.org; Sun, 25 Sep 2005 07:22:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05875
	for <v6ops-archive@ietf.org>; Sun, 25 Sep 2005 07:22:12 -0400 (EDT)
Received: from [200.66.227.203] (helo=obsidiana.com.ar)
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1EJUgw-0002y2-RY
	for v6ops-archive@ietf.org; Sun, 25 Sep 2005 07:29:17 -0400
From: "Mays Marcelino" <Henrique@tvnet.lv>
To: "Mcallister Marcelo" <v6ops-archive@ietf.org>
Subject: Re[9]:
Date: Sun, 25 Sep 2005 11:22:11 +0000
Message-ID: <3fb901c5c1c3$0f24199a$9cff9725@obsidiana.com.ar>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_1F62_7A89B53D.40CE1F62"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4942.400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4942.400
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2

This is a multi-part message in MIME format.

------=_NextPart_000_1F62_7A89B53D.40CE1F62
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

SPUR-m [Sperm pills] - it will work out!

SPUR-m [Cum pills]: http://inaptness.com/

------=_NextPart_000_1F62_7A89B53D.40CE1F62
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
SPUR-m [Sperm pills] - it will work out!
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>SPUR-m [Cum pills]: <A=20
href=3D"http://inaptness.com/">http://inaptness.com/</A></FONT></DIV>
</BODY></HTML>

------=_NextPart_000_1F62_7A89B53D.40CE1F62--




From owner-v6ops@ops.ietf.org Mon Sep 26 17:43:18 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EK0ko-0007OS-JX
	for v6ops-archive@megatron.ietf.org; Mon, 26 Sep 2005 17:43:18 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13062
	for <v6ops-archive@lists.ietf.org>; Mon, 26 Sep 2005 17:43:15 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.52 (FreeBSD))
	id 1EK0hO-0003dd-KJ
	for v6ops-data@psg.com; Mon, 26 Sep 2005 21:39:46 +0000
Received: from [204.202.242.24] (helo=mail19a.g19.rapidsite.net)
	by psg.com with smtp (Exim 4.52 (FreeBSD))
	id 1EK0hL-0003dJ-4o
	for v6ops@ops.ietf.org; Mon, 26 Sep 2005 21:39:43 +0000
Received: from mx02.stngva01.us.mxservers.net (204.202.242.66)
	by mail19a.g19.rapidsite.net (RS ver 1.0.95vs) with SMTP id 2-0638464212
	for <v6ops@ops.ietf.org>; Mon, 26 Sep 2005 10:16:52 -0400 (EDT)
Received: from www.native6.com [198.170.236.53] (EHLO JSN6LT)
	by mx02.stngva01.us.mxservers.net (mxl_mta-1.3.8-10p4) with ESMTP id 4d208334.13779.335.mx02.stngva01.us.mxservers.net;
	Mon, 26 Sep 2005 10:16:52 -0400 (EDT)
From: "John Spence" <jspence@native6.com>
To: <v6ops@ops.ietf.org>
Subject: ISATAP interface ... if PRL is empty disable interface?
Date: Mon, 26 Sep 2005 07:16:48 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcXCpO1YDbnwfdY9TheKvnZGhGxsTQ==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-Spam: [F=0.0911175190; heur=0.908(4300); stat=0.010; spamtraq-heur=0.500(2005092502)]
X-MAIL-FROM: <jspence@native6.com>
X-SOURCE-IP: [198.170.236.53]
Message-ID: <20050926101652.GA63846@mail19a.g19.rapidsite.net>
X-Loop-Detect: 1
X-DistLoop-Detect: 1
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


v24 of the ISATAP spec, 8.3.2, says that:

"After initializing an ISATAP interface's PRL, if the PRL is
empty the node SHOULD disable the interface."

Just because there is no default router, ISATAP client nodes can
exchange traffic using their link-local addresses on the virtual
ISATAP link.  That would be consistent with native nodes - just
because they have no router, and no way off the link, they still
configure link-local addresses and stand ready to talk to other
nodes that are on-link - they do not disable the interface.

Is there something else in the Spec I missed that allows nodes to
communicate using link-local addresses in the absence of an
ISATAP router?

John Spence
----------------------------------------------------
John Spence, CCSI, CCNA, CISSP
Native6, Inc.
IPv6 Training and Consulting
jspence@native6.com
(wk) 206-682-0275
www.native6.com
----------------------------------------------------





From owner-v6ops@ops.ietf.org Tue Sep 27 18:53:28 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKOKG-0000jE-8k
	for v6ops-archive@megatron.ietf.org; Tue, 27 Sep 2005 18:53:28 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26888
	for <v6ops-archive@lists.ietf.org>; Tue, 27 Sep 2005 18:53:25 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.52 (FreeBSD))
	id 1EKOHU-000AGt-IK
	for v6ops-data@psg.com; Tue, 27 Sep 2005 22:50:36 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on psg.com
X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00,FORGED_RCVD_HELO,
	RCVD_NUMERIC_HELO,UNPARSEABLE_RELAY autolearn=no version=3.1.0
Received: from [192.18.98.36] (helo=brmea-mail-4.sun.com)
	by psg.com with esmtp (Exim 4.52 (FreeBSD))
	id 1EKOHT-000AGW-Sn
	for v6ops@ops.ietf.org; Tue, 27 Sep 2005 22:50:35 +0000
Received: from phys-bur1-1 ([129.148.13.15])
	by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id j8RMoYvH022940
	for <v6ops@ops.ietf.org>; Tue, 27 Sep 2005 16:50:35 -0600 (MDT)
Received: from conversion-daemon.bur-mail2.east.sun.com by
 bur-mail2.east.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003))
 id <0INH00601ZE2KV@bur-mail2.east.sun.com>
 (original mail from Sebastien.Roy@Sun.COM) for v6ops@ops.ietf.org; Tue,
 27 Sep 2005 18:50:34 -0400 (EDT)
Received: from 129.148.174.103 (strat.East.Sun.COM [129.148.174.103])
 by bur-mail2.east.sun.com
 (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003))
 with ESMTP id <0INH00MBGZGAEU@bur-mail2.east.sun.com>; Tue,
 27 Sep 2005 18:50:34 -0400 (EDT)
Date: Tue, 27 Sep 2005 18:50:34 -0400
From: Sebastien Roy <Sebastien.Roy@Sun.COM>
Subject: RE: Link Adaptation for IPv6-in-IPv4 Tunnels
In-reply-to: 
 <39C363776A4E8C4A94691D2BD9D1C9A10D5049@XCH-NW-7V2.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Cc: Fred Baker <fred@cisco.com>, v6ops@ops.ietf.org
Message-id: <1127861434.14641.97.camel@strat.East.Sun.COM>
Organization: Solaris Network & Security Technologies, Sun Microsystems
MIME-version: 1.0
X-Mailer: Ximian Evolution 1.4.6.323
Content-type: text/plain
Content-transfer-encoding: 7BIT
References: 
 <39C363776A4E8C4A94691D2BD9D1C9A10D5049@XCH-NW-7V2.nw.nos.boeing.com>
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7BIT

On Fri, 2005-09-23 at 12:04, Templin, Fred L wrote:
> Can this work be contributed as an extension to [MECH]?

Could this method also be used for IPv4-in-IPv4 tunneling?  I don't see
why the document restricts the algorithm to IPv6-in-IPv4, but I may be
missing something.
-Seb






From owner-v6ops@ops.ietf.org Tue Sep 27 20:05:22 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKPRq-0001Ul-L2
	for v6ops-archive@megatron.ietf.org; Tue, 27 Sep 2005 20:05:22 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29655
	for <v6ops-archive@lists.ietf.org>; Tue, 27 Sep 2005 20:05:21 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.52 (FreeBSD))
	id 1EKPNh-000GNt-LG
	for v6ops-data@psg.com; Wed, 28 Sep 2005 00:01:05 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,
	MSGID_FROM_MTA_HEADER,SPF_HELO_PASS autolearn=ham version=3.1.0
Received: from [65.54.161.41] (helo=hotmail.com)
	by psg.com with esmtp (Exim 4.52 (FreeBSD))
	id 1EKPNg-000GNf-Qs
	for v6ops@ops.ietf.org; Wed, 28 Sep 2005 00:01:04 +0000
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 27 Sep 2005 17:01:04 -0700
Message-ID: <BAY106-F314086FD6646677C039C8EE58D0@phx.gbl>
Received: from 65.54.161.209 by by106fd.bay106.hotmail.msn.com with HTTP;
	Wed, 28 Sep 2005 00:01:04 GMT
X-Originating-IP: [65.54.161.209]
X-Originating-Email: [amin_abdul@hotmail.com]
X-Sender: amin_abdul@hotmail.com
From: "Amin Abdul" <amin_abdul@hotmail.com>
To: v6ops@ops.ietf.org
Subject: Interaction between IPv6 and middle boxes
Date: Wed, 28 Sep 2005 00:01:04 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-OriginalArrivalTime: 28 Sep 2005 00:01:04.0452 (UTC) FILETIME=[B8159840:01C5C3BF]
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk

Hi,
I am looking for an IETF document(s) which explains an interaction between 
IPv6 and middle boxes, such as:

1. Interaction between IPv6 and OPES (Open Pluggable Edge Services, i.e. Web 
caching, virus scanning, request filtering and Content Adaptation)
2. Interaction between IPv6 and Intrusion Detection Systems

Would you please point to the appropriate document(s).

Thanks,
Amin






From owner-v6ops@ops.ietf.org Wed Sep 28 00:09:45 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKTGK-0001PM-Ui
	for v6ops-archive@megatron.ietf.org; Wed, 28 Sep 2005 00:09:45 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11956
	for <v6ops-archive@lists.ietf.org>; Wed, 28 Sep 2005 00:09:42 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.52 (FreeBSD))
	id 1EKTDB-000Aw8-1E
	for v6ops-data@psg.com; Wed, 28 Sep 2005 04:06:29 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.1.0
Received: from [171.71.176.72] (helo=sj-iport-3.cisco.com)
	by psg.com with esmtp (Exim 4.52 (FreeBSD))
	id 1EKTD7-000Avl-Vs
	for v6ops@ops.ietf.org; Wed, 28 Sep 2005 04:06:26 +0000
Received: from hkg-core-1.cisco.com ([64.104.123.94])
  by sj-iport-3.cisco.com with ESMTP; 27 Sep 2005 21:06:25 -0700
X-IronPort-AV: i="3.97,152,1125903600"; 
   d="scan'208"; a="346172440:sNHT32053708"
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com [64.104.123.72])
	by hkg-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j8S45pgm008778;
	Wed, 28 Sep 2005 12:06:13 +0800 (CST)
Received: from xmb-hkg-417.apac.cisco.com ([64.104.123.89]) by xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.0);
	 Wed, 28 Sep 2005 12:06:12 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: ISATAP interface ... if PRL is empty disable interface?
Date: Wed, 28 Sep 2005 12:06:11 +0800
Message-ID: <FA36DA862CCB4B4B99765E60671E7BB96BB315@xmb-hkg-417.apac.cisco.com>
Thread-Topic: ISATAP interface ... if PRL is empty disable interface?
Thread-Index: AcXCpO1YDbnwfdY9TheKvnZGhGxsTQBOrtsw
From: "Tim Gleeson \(tgleeson\)" <tgleeson@cisco.com>
To: "John Spence" <jspence@native6.com>, <v6ops@ops.ietf.org>
X-OriginalArrivalTime: 28 Sep 2005 04:06:12.0432 (UTC) FILETIME=[F6B93D00:01C5C3E1]
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

John,

The SHOULD NOT is there to discourage use of ISATAP on the Internet when
the PRL is empty. However, since it is a SHOULD NOT, within a site one
can configure ISATAP to be used anyway.

Tim

> -----Original Message-----
> From: owner-v6ops@ops.ietf.org=20
> [mailto:owner-v6ops@ops.ietf.org] On Behalf Of John Spence
> Sent: Monday, September 26, 2005 11:17 PM
> To: v6ops@ops.ietf.org
> Subject: ISATAP interface ... if PRL is empty disable interface?
>=20
>=20
> v24 of the ISATAP spec, 8.3.2, says that:
>=20
> "After initializing an ISATAP interface's PRL, if the PRL is=20
> empty the node SHOULD disable the interface."
>=20
> Just because there is no default router, ISATAP client nodes=20
> can exchange traffic using their link-local addresses on the=20
> virtual ISATAP link.  That would be consistent with native=20
> nodes - just because they have no router, and no way off the=20
> link, they still configure link-local addresses and stand=20
> ready to talk to other nodes that are on-link - they do not=20
> disable the interface.
>=20
> Is there something else in the Spec I missed that allows=20
> nodes to communicate using link-local addresses in the=20
> absence of an ISATAP router?
>=20
> John Spence
> ----------------------------------------------------
> John Spence, CCSI, CCNA, CISSP
> Native6, Inc.
> IPv6 Training and Consulting
> jspence@native6.com
> (wk) 206-682-0275
> www.native6.com
> ----------------------------------------------------
>=20




From owner-v6ops@ops.ietf.org Wed Sep 28 10:57:58 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EKdNe-0006jS-9G
	for v6ops-archive@megatron.ietf.org; Wed, 28 Sep 2005 10:57:58 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12920
	for <v6ops-archive@lists.ietf.org>; Wed, 28 Sep 2005 10:57:56 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.52 (FreeBSD))
	id 1EKdK8-000DWX-AQ
	for v6ops-data@psg.com; Wed, 28 Sep 2005 14:54:20 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham 
	version=3.1.0
Received: from [204.202.242.24] (helo=mail19a.g19.rapidsite.net)
	by psg.com with smtp (Exim 4.52 (FreeBSD))
	id 1EKdJz-000DU4-Bl
	for v6ops@ops.ietf.org; Wed, 28 Sep 2005 14:54:11 +0000
Received: from mx25.stngva01.us.mxservers.net (204.202.242.72)
	by mail19a.g19.rapidsite.net (RS ver 1.0.95vs) with SMTP id 3-0527119248;
	Wed, 28 Sep 2005 10:54:09 -0400 (EDT)
Received: from www.native6.com [198.170.236.53] (EHLO JSN6LT)
	by mx25.stngva01.us.mxservers.net (mxl_mta-1.3.8-10p4) with ESMTP id 09eaa334.12046.113.mx25.stngva01.us.mxservers.net;
	Wed, 28 Sep 2005 10:54:08 -0400 (EDT)
From: "John Spence" <jspence@native6.com>
To: "'Tim Gleeson \(tgleeson\)'" <tgleeson@cisco.com>, <v6ops@ops.ietf.org>
Subject: RE: ISATAP interface ... if PRL is empty disable interface?
Date: Wed, 28 Sep 2005 07:54:06 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
Thread-Index: AcXCpO1YDbnwfdY9TheKvnZGhGxsTQBOrtswABcm7PA=
In-Reply-To: <FA36DA862CCB4B4B99765E60671E7BB96BB315@xmb-hkg-417.apac.cisco.com>
X-Spam: [F=0.0043103448; heur=0.500(-2300); stat=0.010; spamtraq-heur=0.300(2005092802)]
X-MAIL-FROM: <jspence@native6.com>
X-SOURCE-IP: [198.170.236.53]
Message-ID: <20050928105409.GA52711@mail19a.g19.rapidsite.net>
X-Loop-Detect: 1
X-DistLoop-Detect: 1
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Fair enough.  Thanks for the response Tim.

Spence 

> -----Original Message-----
> From: Tim Gleeson (tgleeson) [mailto:tgleeson@cisco.com] 
> Sent: Tuesday, September 27, 2005 9:06 PM
> To: John Spence; v6ops@ops.ietf.org
> Subject: RE: ISATAP interface ... if PRL is empty disable
interface?
> 
> John,
> 
> The SHOULD NOT is there to discourage use of ISATAP on the 
> Internet when the PRL is empty. However, since it is a SHOULD 
> NOT, within a site one can configure ISATAP to be used anyway.
> 
> Tim
> 
> > -----Original Message-----
> > From: owner-v6ops@ops.ietf.org
> > [mailto:owner-v6ops@ops.ietf.org] On Behalf Of John Spence
> > Sent: Monday, September 26, 2005 11:17 PM
> > To: v6ops@ops.ietf.org
> > Subject: ISATAP interface ... if PRL is empty disable
interface?
> > 
> > 
> > v24 of the ISATAP spec, 8.3.2, says that:
> > 
> > "After initializing an ISATAP interface's PRL, if the PRL 
> is empty the 
> > node SHOULD disable the interface."
> > 
> > Just because there is no default router, ISATAP client nodes
can 
> > exchange traffic using their link-local addresses on the
virtual 
> > ISATAP link.  That would be consistent with native nodes -
just 
> > because they have no router, and no way off the link, they
still 
> > configure link-local addresses and stand ready to talk to 
> other nodes 
> > that are on-link - they do not disable the interface.
> > 
> > Is there something else in the Spec I missed that allows
nodes to 
> > communicate using link-local addresses in the absence of an
ISATAP 
> > router?





From owner-v6ops@ops.ietf.org Fri Sep 30 18:44:27 2005
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ELTcA-0007WW-3r
	for v6ops-archive@megatron.ietf.org; Fri, 30 Sep 2005 18:44:27 -0400
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24142
	for <v6ops-archive@lists.ietf.org>; Fri, 30 Sep 2005 18:44:23 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.52 (FreeBSD))
	id 1ELTXp-0003Bx-PW
	for v6ops-data@psg.com; Fri, 30 Sep 2005 22:39:57 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on psg.com
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=3.1.0
Received: from [130.76.96.56] (helo=stl-smtpout-01.boeing.com)
	by psg.com with esmtp (Exim 4.52 (FreeBSD))
	id 1ELTXo-0003Bl-VR
	for v6ops@ops.ietf.org; Fri, 30 Sep 2005 22:39:57 +0000
Received: from blv-av-01.boeing.com ([192.42.227.216])
	by stl-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id RAA01403;
	Fri, 30 Sep 2005 17:39:55 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id j8UMdtx26025;
	Fri, 30 Sep 2005 15:39:55 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830);
	 Fri, 30 Sep 2005 15:39:53 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Requirements for Link Adaptation over IP-in-IPv4 Tunnels (was RE: Link Adaptation for IPv6-in-IPv4 Tunnels) 
Date: Fri, 30 Sep 2005 15:39:52 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A10D5075@XCH-NW-7V2.nw.nos.boeing.com>
Thread-Topic: Requirements for Link Adaptation over IP-in-IPv4 Tunnels (was RE: Link Adaptation for IPv6-in-IPv4 Tunnels) 
Thread-Index: AcXAW1x+TtPa9HKuRSa+/F0sREjUuQFs2JTA
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Fred Baker" <fred@cisco.com>
Cc: <v6ops@ops.ietf.org>
X-OriginalArrivalTime: 30 Sep 2005 22:39:53.0050 (UTC) FILETIME=[DFBDE3A0:01C5C60F]
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Fred - please see:

http://www.ietf.org/internet-drafts/draft-templin-linkadapt-reqts-00.txt

Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: Fred Baker [mailto:fred@cisco.com]=20
> Sent: Friday, September 23, 2005 9:24 AM
> To: Templin, Fred L
> Cc: v6ops@ops.ietf.org
> Subject: Re: Link Adaptation for IPv6-in-IPv4 Tunnels=20
>=20
> Does it still propose a protocol or protocol change?
>=20
> I don't know offhand whether the charter of v6ops then precluded =20
> protocol work, and won't go into whether it was proper for [MECH] to =20
> be done in v6ops. Given the present charter, I can treat it as a =20
> requirements document that may be asking for something like the work =20
> you are proposing. But my read of the document you pointed to=20
> is that =20
> it is still proposing an incompatible change (as in "unchanged =20
> equipment will not perform the function and once the message is =20
> segmented in this fashion it must be reassembled in this fashion.
>=20
> I think that has to be done in a WG chartered to do non-backward-=20
> compatible changes to IPv4.
>=20
> On Sep 23, 2005, at 9:04 AM, Templin, Fred L wrote:
>=20
> > Can this work be contributed as an extension to [MECH]?
> >
>=20




