Fwd: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt

Bill Manning <bmanning@karoshi.com> Fri, 16 September 2005 21:56 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EGOBk-0001lD-Vc; Fri, 16 Sep 2005 17:56:08 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EGOBh-0001l0-O6; Fri, 16 Sep 2005 17:56:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21515; Fri, 16 Sep 2005 17:56:02 -0400 (EDT)
Received: from felix.hopcount.ca ([] helo=felix.automagic.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EGOGg-0005Go-MX; Fri, 16 Sep 2005 18:01:21 -0400
Received: from [] (helo=[]) by felix.automagic.org with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42 (FreeBSD)) id 1EGOBI-000Pl8-W0; Fri, 16 Sep 2005 21:55:41 +0000
Mime-Version: 1.0 (Apple Message framework v622)
To: IETF General Discussion Mailing List <ietf@ietf.org>, ipv6@ietf.org
Message-Id: <c982b04fe919ffd634c99faf685bed82@karoshi.com>
From: Bill Manning <bmanning@karoshi.com>
Date: Fri, 16 Sep 2005 14:55:38 -0700
X-Mailer: Apple Mail (2.622)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bfe538a859d88717fa3c8a6377d62f90
Cc: bill manning <bmanning@ep.net>
Subject: Fwd: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1466272726=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

sorry, the I-D has no information as to where this should be  
discussed... so:

i am convinced that the IETF has no business telling me what routes i  
may or may not
accept from or send to my peers, with the exception of prefixes of  
undefined BEHAVIOUR,
much like the IPv4 class "E" space.  That said,  if these are  
Guidelines, as the title suggests,
then there is no place for  the "MUST/MAY/SHOULD" keywords.   Even now,  
within the RIR
and operational communities, there are discussions on changing the /48  

this draft should be abandon, imho.  if kept, it needs serious surgery.


Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: September 16, 2005 12:50:02 PDT
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-blanchet-v6ops-routing-guidelines-00.txt
> Reply-To: internet-drafts@ietf.org
> A New Internet-Draft is available from the on-line Internet-Drafts  
> 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 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  
> 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 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
Ietf mailing list