
From internet-drafts@ietf.org  Tue Aug  2 07:27:23 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CCC311E807B; Tue,  2 Aug 2011 07:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wAdtii5WbzE0; Tue,  2 Aug 2011 07:27:22 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67F5621F84F9; Tue,  2 Aug 2011 07:27:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.57
Message-ID: <20110802142722.21798.86499.idtracker@ietfa.amsl.com>
Date: Tue, 02 Aug 2011 07:27:22 -0700
Cc: int-area@ietf.org
Subject: [Int-area] I-D Action: draft-ietf-intarea-router-alert-considerations-08.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 14:27:23 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Internet Area Working Group Working G=
roup of the IETF.

	Title           : IP Router Alert Considerations and Usage
	Author(s)       : Francois Le Faucheur
	Filename        : draft-ietf-intarea-router-alert-considerations-08.txt
	Pages           : 24
	Date            : 2011-08-02

   The IP Router Alert Option is an IP option that alerts transit
   routers to more closely examine the contents of an IP packet.
   Resource reSerVation Protocol (RSVP), Pragmatic General Multicast
   (PGM), Internet Group Management Protocol (IGMP), Multicast Listener
   Discovery (MLD), Multicast Router Discovery (MRD) and General
   Internet Signalling Transport (GIST) are some of the protocols that
   make use of the IP Router Alert Option.  This document discusses
   security aspects and usage guidelines around the use of the current
   IP Router Alert Option.  Specifically, it provides recommendation
   against using the Router Alert in the end-to-end open Internet as
   well as identify controlled environments where protocols depending on
   Router Alert can be used safely.  It also provides recommendation
   about protection approaches for Service Providers.  Finally it
   provides brief guidelines for Router Alert implementation on routers.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-intarea-router-alert-conside=
rations-08.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-intarea-router-alert-consider=
ations-08.txt

From internet-drafts@ietf.org  Tue Aug  2 07:34:42 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0186711E808A; Tue,  2 Aug 2011 07:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y3Cg037hL5Hz; Tue,  2 Aug 2011 07:34:41 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AFCE11E8080; Tue,  2 Aug 2011 07:34:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.57
Message-ID: <20110802143441.22517.81807.idtracker@ietfa.amsl.com>
Date: Tue, 02 Aug 2011 07:34:41 -0700
Cc: int-area@ietf.org
Subject: [Int-area] I-D Action: draft-ietf-intarea-router-alert-considerations-09.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2011 14:34:42 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Internet Area Working Group Working G=
roup of the IETF.

	Title           : IP Router Alert Considerations and Usage
	Author(s)       : Francois Le Faucheur
	Filename        : draft-ietf-intarea-router-alert-considerations-09.txt
	Pages           : 24
	Date            : 2011-08-02

   The IP Router Alert Option is an IP option that alerts transit
   routers to more closely examine the contents of an IP packet.
   Resource reSerVation Protocol (RSVP), Pragmatic General Multicast
   (PGM), Internet Group Management Protocol (IGMP), Multicast Listener
   Discovery (MLD), Multicast Router Discovery (MRD) and General
   Internet Signalling Transport (GIST) are some of the protocols that
   make use of the IP Router Alert Option.  This document discusses
   security aspects and usage guidelines around the use of the current
   IP Router Alert Option.  Specifically, it provides recommendation
   against using the Router Alert in the end-to-end open Internet as
   well as identify controlled environments where protocols depending on
   Router Alert can be used safely.  It also provides recommendation
   about protection approaches for Service Providers.  Finally it
   provides brief guidelines for Router Alert implementation on routers.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-intarea-router-alert-conside=
rations-09.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-intarea-router-alert-consider=
ations-09.txt

From internet-drafts@ietf.org  Wed Aug  3 11:11:07 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8102021F8A58; Wed,  3 Aug 2011 11:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F0YqJmT0Q+C6; Wed,  3 Aug 2011 11:11:07 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5AFB21F898E; Wed,  3 Aug 2011 11:11:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.57
Message-ID: <20110803181106.5324.44046.idtracker@ietfa.amsl.com>
Date: Wed, 03 Aug 2011 11:11:06 -0700
Cc: int-area@ietf.org
Subject: [Int-area] I-D Action: draft-ietf-intarea-router-alert-considerations-10.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 18:11:07 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Internet Area Working Group Working G=
roup of the IETF.

	Title           : IP Router Alert Considerations and Usage
	Author(s)       : Francois Le Faucheur
	Filename        : draft-ietf-intarea-router-alert-considerations-10.txt
	Pages           : 24
	Date            : 2011-08-03

   The IP Router Alert Option is an IP option that alerts transit
   routers to more closely examine the contents of an IP packet.
   Resource reSerVation Protocol (RSVP), Pragmatic General Multicast
   (PGM), Internet Group Management Protocol (IGMP), Multicast Listener
   Discovery (MLD), Multicast Router Discovery (MRD) and General
   Internet Signalling Transport (GIST) are some of the protocols that
   make use of the IP Router Alert Option.  This document discusses
   security aspects and usage guidelines around the use of the current
   IP Router Alert Option thereby updating RFC2113 and RFC2711.
   Specifically, it provides recommendation against using the Router
   Alert in the end-to-end open Internet as well as identify controlled
   environments where protocols depending on Router Alert can be used
   safely.  It also provides recommendation about protection approaches
   for Service Providers.  Finally it provides brief guidelines for
   Router Alert implementation on routers.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-intarea-router-alert-conside=
rations-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-intarea-router-alert-consider=
ations-10.txt

From Fred.L.Templin@boeing.com  Fri Aug  5 16:56:31 2011
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A22AE21F8AD1 for <int-area@ietfa.amsl.com>; Fri,  5 Aug 2011 16:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.433
X-Spam-Level: 
X-Spam-Status: No, score=-6.433 tagged_above=-999 required=5 tests=[AWL=0.166,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7K44i-v1XiBO for <int-area@ietfa.amsl.com>; Fri,  5 Aug 2011 16:56:31 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by ietfa.amsl.com (Postfix) with ESMTP id D795221F8ACE for <int-area@ietf.org>; Fri,  5 Aug 2011 16:56:30 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p75Nuft5011101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <int-area@ietf.org>; Fri, 5 Aug 2011 18:56:47 -0500 (CDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p75Nufe7029551 for <int-area@ietf.org>; Fri, 5 Aug 2011 18:56:41 -0500 (CDT)
Received: from XCH-NWHT-08.nw.nos.boeing.com (xch-nwht-08.nw.nos.boeing.com [130.247.25.112]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p75Nuffj029539 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for <int-area@ietf.org>; Fri, 5 Aug 2011 18:56:41 -0500 (CDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-08.nw.nos.boeing.com ([130.247.25.112]) with mapi; Fri, 5 Aug 2011 16:56:40 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "int-area@ietf.org" <int-area@ietf.org>
Date: Fri, 5 Aug 2011 16:56:38 -0700
Thread-Topic: IRON - a new version with new insights
Thread-Index: AcxTxlXy9gHZULeBSuOdFscF0NAxaQAAF3oQ
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C770275F6@XCH-NW-01V.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [Int-area] IRON - a new version with new insights
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 23:56:31 -0000

Hello,

As you know, IRON [RFC6179] is a product of the IRTF
Routing Research Group. We have since discussed its
applicability in the Intarea, and I have therefore
decided to create a (bis) version to move beyond the
IRTF research realm and into practical aspects of
interest to the IETF.

See below for an announcement of the (bis). This
version is in many ways a simplification of the RRG
work, and removes aspects that would impede or limit
applicability. The new version observes that the IRON
deployment model parallels the numerous successful
IPv6 tunnelbroker network deployments which today
provide a robust IPv6 service to clients. These
examples therfore provide existence proofs that
key aspects of the IRON approach are feasible.

The IRON Client/Server relationship is in fact a very
close parallel to tunnel broker. However, IRON also
provides a route optimization capability that combines
the best aspects of tunnelbroker and NBMA automatic
tunneling. IRON in fact reaches well beyond the basic
tunnelbroker service model and tackles key features
of interest to Intarea including mobility, multiple
interfaces, traffic engineering, IPv6 addressing, etc.

Again, this is a new IRON with new insights for this
group to consider. In terms of technology maturity
levels, the goal of this effort is to move the needle
beyond "discovery" and to make deep advances into
"practicality". I welcome your comments.

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

-----Original Message-----
From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] =
On Behalf Of internet-drafts@ietf.org
Sent: Friday, August 05, 2011 4:20 PM
To: i-d-announce@ietf.org
Subject: I-D Action: draft-templin-ironbis-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.

	Title           : The Internet Routing Overlay Network (IRON)
	Author(s)       : Fred L. Templin
	Filename        : draft-templin-ironbis-01.txt
	Pages           : 39
	Date            : 2011-08-05

   Since the Internet must continue to support escalating growth due to
   increasing demand, it is clear that current routing architectures and
   operational practices must be updated.  This document proposes an
   Internet Routing Overlay Network (IRON) architecture that supports
   sustainable growth while requiring no changes to end systems and no
   changes to the existing routing system.  IRON further addresses other
   important issues including routing scaling, mobility management,
   multihoming, traffic engineering and NAT traversal.  While business
   considerations are an important determining factor for widespread
   adoption, they are out of scope for this document.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-templin-ironbis-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-templin-ironbis-01.txt
_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

From jari.arkko@piuha.net  Fri Aug 19 11:01:13 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DB6021F8B51 for <int-area@ietfa.amsl.com>; Fri, 19 Aug 2011 11:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.563
X-Spam-Level: 
X-Spam-Status: No, score=-102.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JV-Gw4-4qfjU for <int-area@ietfa.amsl.com>; Fri, 19 Aug 2011 11:01:12 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id C1D2421F8B4E for <int-area@ietf.org>; Fri, 19 Aug 2011 11:01:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id B76222CEFF; Fri, 19 Aug 2011 21:02:09 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0rPW0CH0XfSe; Fri, 19 Aug 2011 21:02:09 +0300 (EEST)
Received: from [IPv6:::1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 425D52CE12; Fri, 19 Aug 2011 21:02:09 +0300 (EEST)
Message-ID: <4E4EA520.6030506@piuha.net>
Date: Fri, 19 Aug 2011 21:02:08 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: draft-ietf-intarea-ipv6-required@tools.ietf.org,  Internet Area <int-area@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Int-area] AD review of draft-ietf-intarea-ipv6-required
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 18:01:13 -0000

I have reviewed this draft, found it ready to move forward, and sent it 
to IETF Last Call. Thanks for writing this draft.

I only had a very minor editorial comment:

> IPv6 [RFC1883 <http://tools.ietf.org/html/rfc1883>] was proposed in 1995 as, among other things, a
> solution to the limitations on globally unique addressing that IPv4's
> 32-bit addressing space represented, and has been under continuous
> refinement and deployment ever since.  [RFC2460 <http://tools.ietf.org/html/rfc2460>]. 

s/.  [RFC2460]/ [RFC2460]/

(I think, it was not clear to me why you placed a reference here.)

Jari


From iesg-secretary@ietf.org  Fri Aug 19 11:33:06 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0813E11E80A2; Fri, 19 Aug 2011 11:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.397
X-Spam-Level: 
X-Spam-Status: No, score=-102.397 tagged_above=-999 required=5 tests=[AWL=0.202, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CHfpde2XJIlj; Fri, 19 Aug 2011 11:33:05 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9708D21F8B7F; Fri, 19 Aug 2011 11:33:05 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.59
Message-ID: <20110819183305.27249.79870.idtracker@ietfa.amsl.com>
Date: Fri, 19 Aug 2011 11:33:05 -0700
Cc: int-area@ietf.org
Subject: [Int-area] Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Support	Required for all IP-capable nodes) to Proposed Standard
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 18:33:06 -0000

The IESG has received a request from the Internet Area Working Group WG
(intarea) to consider the following document:
- 'IPv6 Support Required for all IP-capable nodes'
  <draft-ietf-intarea-ipv6-required-01.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2011-09-02. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   Given the global lack of available IPv4 space, and limitations in
   IPv4 extension and transition technologies, this document deprecates
   the concept that an IP-capable node MAY support IPv4 _only_, and
   redefines an IP-capable node as one which supports either IPv6 _only_
   or IPv4/IPv6 dual-stack.  This document updates RFC1812, RFC1122 and
   RFC4084 to reflect the change in requirements.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-intarea-ipv6-required/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-intarea-ipv6-required/


No IPR declarations have been submitted directly on this I-D.



From brian.e.carpenter@gmail.com  Fri Aug 19 16:14:36 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3045221F8B3D; Fri, 19 Aug 2011 16:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.593
X-Spam-Level: 
X-Spam-Status: No, score=-103.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RDUI1SL4v8mF; Fri, 19 Aug 2011 16:14:35 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 459AA21F8B2D; Fri, 19 Aug 2011 16:14:35 -0700 (PDT)
Received: by fxe6 with SMTP id 6so2451482fxe.31 for <multiple recipients>; Fri, 19 Aug 2011 16:15:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=eWAWsUL7qjefJDbMfj+WATTKqv5S/19Rimk0vmLXXf4=; b=CdueHvFMQCpEovvQCibJ/naB4TlYaOeAv6UptNLDLyU0pltMA13sESEdUzfOJd32dP RfL/JRGi34OAD+/JLezxu6a7Es99QZmPFVTPb02ckmBu1aAm2nYmeUevG5SOajdstgul fJPUYWe7jBPtqgFZc1s1Hr3G7v8/366n0b0t8=
Received: by 10.223.61.211 with SMTP id u19mr363326fah.102.1313795732624; Fri, 19 Aug 2011 16:15:32 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id e5sm2004430fah.11.2011.08.19.16.15.29 (version=SSLv3 cipher=OTHER); Fri, 19 Aug 2011 16:15:31 -0700 (PDT)
Message-ID: <4E4EEE8C.6050102@gmail.com>
Date: Sat, 20 Aug 2011 11:15:24 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
References: <20110819183305.27249.79870.idtracker@ietfa.amsl.com>
In-Reply-To: <20110819183305.27249.79870.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: int-area@ietf.org
Subject: Re: [Int-area] Last Call: <draft-ietf-intarea-ipv6-required-01.txt> (IPv6 Support Required for all IP-capable nodes) to Proposed Standard
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2011 23:14:36 -0000

I fully support this document. It could be tuned in the way
Keith suggested, but basically it is a Good Thing.

Regards
   Brian Carpenter
