
From christopher.morrow@gmail.com  Mon Mar  5 13:21:55 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1668B21E8036 for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 13:21:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.499
X-Spam-Level: 
X-Spam-Status: No, score=-103.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 sddgj75RiQrk for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 13:21:54 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 119AC21E8038 for <grow@ietf.org>; Mon,  5 Mar 2012 13:21:53 -0800 (PST)
Received: by obbta4 with SMTP id ta4so3060418obb.31 for <grow@ietf.org>; Mon, 05 Mar 2012 13:21:52 -0800 (PST)
Received-SPF: pass (google.com: domain of christopher.morrow@gmail.com designates 10.182.1.4 as permitted sender) client-ip=10.182.1.4;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of christopher.morrow@gmail.com designates 10.182.1.4 as permitted sender) smtp.mail=christopher.morrow@gmail.com; dkim=pass header.i=christopher.morrow@gmail.com
Received: from mr.google.com ([10.182.1.4]) by 10.182.1.4 with SMTP id 4mr8603829obi.67.1330982512722 (num_hops = 1); Mon, 05 Mar 2012 13:21:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=s7O2+jvF7czv3Oe9eAuKSU1oN9UKAZhRhYA3rfvnrJw=; b=a1ro0HM5uM0rm0IHuiv0qDuDyamevlQHcS4fXf+3g4EF7G0WPQg1gUqEwmg+2W2NSf QpYv4N18cOM3TFqGqqJkt8QEnnPgkmH5Wpe34QLruY0J82gyE1eQgvok21RGW+/6yaef Vo2ZtgITQxV4L/FmfR1VNLY0641m0UIBm4Iyq/osbvRoT4jiwRIx3aYhSbkIasYaiC3a o2WuyIOvzyCCBZzfWMnsBP+eB9O8vrPdHyN3Ej+xsAbd48Ku70BQf17n/a68zP8Aw80y WGW/VK4CAVnwe9DriBwLSUiygyxQ4WI9HJhbPX+3G9jVJlS/HgFTndJladzM5j/6FZOX UlTw==
MIME-Version: 1.0
Received: by 10.182.1.4 with SMTP id 4mr7554293obi.67.1330982512665; Mon, 05 Mar 2012 13:21:52 -0800 (PST)
Received: by 10.182.139.106 with HTTP; Mon, 5 Mar 2012 13:21:52 -0800 (PST)
In-Reply-To: <5F5784B7-4593-402E-A0E1-EB0047139B2E@secure64.com>
References: <20120228205159.11401.49917.idtracker@ietfa.amsl.com> <5F5784B7-4593-402E-A0E1-EB0047139B2E@secure64.com>
Date: Mon, 5 Mar 2012 16:21:52 -0500
Message-ID: <CAL9jLaYbu35EbxHuqB1RkGehuxY6kLNrtw_hOrNbaHkBAkURBA@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Joseph Gersch <joe.gersch@secure64.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: grow@ietf.org
Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 21:21:55 -0000

It would be helpful to the chairs (at least) to get a sense of the
'room' (list) on this topic, it seems that the focus is really on a
dnsops sort of paper, though interaction could be had in the routing
space as well (or that's an intent of the draft's work).

It's not clear that GROW is the place for this work, but keeping folks
informed isn't a bad plan either (I think).

-chris
(co-chair)

On Tue, Feb 28, 2012 at 3:58 PM, Joseph Gersch <joe.gersch@secure64.com> wr=
ote:
> All,
> =A0 we have submitted a new draft that we would like to present at the Pa=
ris
> IETF meeting.
> Please take the time to send any comments and suggestions regarding this
> idea on using records in =A0the reverse DNS to help secure BGP route orig=
ins.
>
> Best regards,
> =A0 =A0- Joe Gersch, Dan Massey, Eric Osterweil and Lixia Zhang
>
> Begin forwarded message:
>
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
> Date: February 28, 2012 1:51:59 PM MST
> To: joe.gersch@secure64.com
> Cc: lixia@cs.ucla.edu, eosterweil@verisign.com, massey@cs.colostate.edu
>
> A new version of I-D, draft-gersch-grow-revdns-bgp-00.txt has been
> successfully submitted by Joe Gersch and posted to the IETF repository.
>
> Filename: draft-gersch-grow-revdns-bgp
> Revision: 00
> Title: DNS Resource Records for BGP Routing Data
> Creation date: 2012-02-29
> WG ID: Individual Submission
> Number of pages: 22
>
> Abstract:
> =A0=A0This draft proposes the creation of two DNS record types for storin=
g
> =A0=A0BGP routing information in the reverse DNS. =A0The RLOCK record all=
ows
> =A0=A0prefix owners to indicate whether the DNS is being used to publish
> =A0=A0routing data. =A0The SRO record allows operators to indicate whethe=
r an
> =A0=A0IPv4 or IPv6 prefix ought to appear in global routing tables and
> =A0=A0identifies authorized origin Autonomous System Number(s) for that
> =A0=A0prefix. =A0The published data can be used in a variety of contexts =
and
> =A0=A0can be extended to include additional information. =A0This work is =
part
> =A0=A0of an on-going effort and is accessible in an active testbed.
>
>
>
>
> The IETF Secretariat
>
>
> Joseph Gersch
> Chief=A0Operating=A0Officer
> Secure64=A0Software=A0Corporation
>
>
>
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>

From terry.manderson@icann.org  Mon Mar  5 15:40:55 2012
Return-Path: <terry.manderson@icann.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B8BF21E8035 for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 15:40:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.491
X-Spam-Level: 
X-Spam-Status: No, score=-106.491 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 AK6F1OoKz5Dl for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 15:40:53 -0800 (PST)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by ietfa.amsl.com (Postfix) with ESMTP id CB83A21E801E for <grow@ietf.org>; Mon,  5 Mar 2012 15:40:53 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Mon, 5 Mar 2012 15:40:53 -0800
From: Terry Manderson <terry.manderson@icann.org>
To: Christopher Morrow <christopher.morrow@gmail.com>, Joseph Gersch <joe.gersch@secure64.com>
Date: Mon, 5 Mar 2012 15:40:51 -0800
Thread-Topic: [GROW] Fwd: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
Thread-Index: Acz7Fgy1eruGi2dRTeuXB5i85jBvoAAE1lFd
Message-ID: <CB7B8C23.226F5%terry.manderson@icann.org>
In-Reply-To: <CAL9jLaYbu35EbxHuqB1RkGehuxY6kLNrtw_hOrNbaHkBAkURBA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 23:40:55 -0000

Hi Chris,

I think GROW would be the place to discuss this work.

Yes, it uses DNS and proposes two new RRs ( which will still want some
review from DNS folk for the DNS implementation side ) but I feel it has a
more directed focus into global routing ops with a security lens. With the
absence of a generic 'routing security' WG and the very tight focus of SIDR
on one particular technology by charter, GROW appears to me to be the most
sane choice.

Cheers
Terry




On 6/03/12 7:21 AM, "Christopher Morrow" <christopher.morrow@gmail.com>
wrote:

> It would be helpful to the chairs (at least) to get a sense of the
> 'room' (list) on this topic, it seems that the focus is really on a
> dnsops sort of paper, though interaction could be had in the routing
> space as well (or that's an intent of the draft's work).
>=20
> It's not clear that GROW is the place for this work, but keeping folks
> informed isn't a bad plan either (I think).
>=20
> -chris
> (co-chair)
>=20
> On Tue, Feb 28, 2012 at 3:58 PM, Joseph Gersch <joe.gersch@secure64.com>
> wrote:
>> All,
>> =A0 we have submitted a new draft that we would like to present at the P=
aris
>> IETF meeting.
>> Please take the time to send any comments and suggestions regarding this
>> idea on using records in =A0the reverse DNS to help secure BGP route ori=
gins.
>>=20
>> Best regards,
>> =A0 =A0- Joe Gersch, Dan Massey, Eric Osterweil and Lixia Zhang
>>=20
>> Begin forwarded message:
>>=20
>> From: internet-drafts@ietf.org
>> Subject: New Version Notification for draft-gersch-grow-revdns-bgp-00.tx=
t
>> Date: February 28, 2012 1:51:59 PM MST
>> To: joe.gersch@secure64.com
>> Cc: lixia@cs.ucla.edu, eosterweil@verisign.com, massey@cs.colostate.edu
>>=20
>> A new version of I-D, draft-gersch-grow-revdns-bgp-00.txt has been
>> successfully submitted by Joe Gersch and posted to the IETF repository.
>>=20
>> Filename: draft-gersch-grow-revdns-bgp
>> Revision: 00
>> Title: DNS Resource Records for BGP Routing Data
>> Creation date: 2012-02-29
>> WG ID: Individual Submission
>> Number of pages: 22
>>=20
>> Abstract:
>> =A0=A0This draft proposes the creation of two DNS record types for stori=
ng
>> =A0=A0BGP routing information in the reverse DNS. =A0The RLOCK record al=
lows
>> =A0=A0prefix owners to indicate whether the DNS is being used to publish
>> =A0=A0routing data. =A0The SRO record allows operators to indicate wheth=
er an
>> =A0=A0IPv4 or IPv6 prefix ought to appear in global routing tables and
>> =A0=A0identifies authorized origin Autonomous System Number(s) for that
>> =A0=A0prefix. =A0The published data can be used in a variety of contexts=
 and
>> =A0=A0can be extended to include additional information. =A0This work is=
 part
>> =A0=A0of an on-going effort and is accessible in an active testbed.
>>=20
>>=20
>>=20
>>=20
>> The IETF Secretariat
>>=20
>>=20
>> Joseph Gersch
>> Chief=A0Operating=A0Officer
>> Secure64=A0Software=A0Corporation
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>=20
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From rbonica@juniper.net  Mon Mar  5 17:12:52 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21E1921F87A9 for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 17:12:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.5
X-Spam-Level: 
X-Spam-Status: No, score=-106.5 tagged_above=-999 required=5 tests=[AWL=0.099,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 5RXJR9bYEeIN for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 17:12:51 -0800 (PST)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id 0F4D921F879C for <grow@ietf.org>; Mon,  5 Mar 2012 17:12:51 -0800 (PST)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKT1VkkOz2sLUsP7gg7J3TjMwbLrnqzIgK@postini.com; Mon, 05 Mar 2012 17:12:51 PST
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 5 Mar 2012 17:12:28 -0800
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 5 Mar 2012 17:12:25 -0800
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Mon, 5 Mar 2012 20:12:24 -0500
From: Ronald Bonica <rbonica@juniper.net>
To: Christopher Morrow <christopher.morrow@gmail.com>, Joseph Gersch <joe.gersch@secure64.com>
Date: Mon, 5 Mar 2012 20:12:23 -0500
Thread-Topic: [GROW] Fwd: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
Thread-Index: Acz7FgIRJ6Ma58kOR8mCxzKK8ng2wgAH73IQ
Message-ID: <13205C286662DE4387D9AF3AC30EF456D767D0BA53@EMBX01-WF.jnpr.net>
References: <20120228205159.11401.49917.idtracker@ietfa.amsl.com> <5F5784B7-4593-402E-A0E1-EB0047139B2E@secure64.com> <CAL9jLaYbu35EbxHuqB1RkGehuxY6kLNrtw_hOrNbaHkBAkURBA@mail.gmail.com>
In-Reply-To: <CAL9jLaYbu35EbxHuqB1RkGehuxY6kLNrtw_hOrNbaHkBAkURBA@mail.gmail.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Fwd: New Version Notification for	draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 01:12:52 -0000

Chris,

This draft appears to be operating in the same area as the origin authentic=
ation work that is currently progressing in SIDR. Shouldn't all of that wor=
k be in one place?

My guess is that it belongs in SIDR.

                                                 Ron


> -----Original Message-----
> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
> Christopher Morrow
> Sent: Monday, March 05, 2012 4:22 PM
> To: Joseph Gersch
> Cc: grow@ietf.org
> Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-
> grow-revdns-bgp-00.txt
>=20
> It would be helpful to the chairs (at least) to get a sense of the
> 'room' (list) on this topic, it seems that the focus is really on a
> dnsops sort of paper, though interaction could be had in the routing
> space as well (or that's an intent of the draft's work).
>=20
> It's not clear that GROW is the place for this work, but keeping folks
> informed isn't a bad plan either (I think).
>=20
> -chris
> (co-chair)
>=20
> On Tue, Feb 28, 2012 at 3:58 PM, Joseph Gersch
> <joe.gersch@secure64.com> wrote:
> > All,
> > =A0 we have submitted a new draft that we would like to present at the
> > Paris IETF meeting.
> > Please take the time to send any comments and suggestions regarding
> > this idea on using records in =A0the reverse DNS to help secure BGP
> route origins.
> >
> > Best regards,
> > =A0 =A0- Joe Gersch, Dan Massey, Eric Osterweil and Lixia Zhang
> >
> > Begin forwarded message:
> >
> > From: internet-drafts@ietf.org
> > Subject: New Version Notification for
> > draft-gersch-grow-revdns-bgp-00.txt
> > Date: February 28, 2012 1:51:59 PM MST
> > To: joe.gersch@secure64.com
> > Cc: lixia@cs.ucla.edu, eosterweil@verisign.com,
> > massey@cs.colostate.edu
> >
> > A new version of I-D, draft-gersch-grow-revdns-bgp-00.txt has been
> > successfully submitted by Joe Gersch and posted to the IETF
> repository.
> >
> > Filename: draft-gersch-grow-revdns-bgp
> > Revision: 00
> > Title: DNS Resource Records for BGP Routing Data Creation date:
> > 2012-02-29 WG ID: Individual Submission Number of pages: 22
> >
> > Abstract:
> > =A0=A0This draft proposes the creation of two DNS record types for
> storing
> > =A0=A0BGP routing information in the reverse DNS. =A0The RLOCK record
> allows
> > =A0=A0prefix owners to indicate whether the DNS is being used to publis=
h
> > =A0=A0routing data. =A0The SRO record allows operators to indicate whet=
her
> > an
> > =A0=A0IPv4 or IPv6 prefix ought to appear in global routing tables and
> > =A0=A0identifies authorized origin Autonomous System Number(s) for that
> > =A0=A0prefix. =A0The published data can be used in a variety of context=
s
> and
> > =A0=A0can be extended to include additional information. =A0This work i=
s
> > part
> > =A0=A0of an on-going effort and is accessible in an active testbed.
> >
> >
> >
> >
> > The IETF Secretariat
> >
> >
> > Joseph Gersch
> > Chief=A0Operating=A0Officer
> > Secure64=A0Software=A0Corporation
> >
> >
> >
> >
> > _______________________________________________
> > GROW mailing list
> > GROW@ietf.org
> > https://www.ietf.org/mailman/listinfo/grow
> >
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From christopher.morrow@gmail.com  Mon Mar  5 17:31:23 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C985621E8033 for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 17:31:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.539
X-Spam-Level: 
X-Spam-Status: No, score=-103.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 3jXAzecm-UgC for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 17:31:23 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 138B421E8012 for <grow@ietf.org>; Mon,  5 Mar 2012 17:31:23 -0800 (PST)
Received: by obbta4 with SMTP id ta4so3321803obb.31 for <grow@ietf.org>; Mon, 05 Mar 2012 17:31:22 -0800 (PST)
Received-SPF: pass (google.com: domain of christopher.morrow@gmail.com designates 10.182.14.97 as permitted sender) client-ip=10.182.14.97; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of christopher.morrow@gmail.com designates 10.182.14.97 as permitted sender) smtp.mail=christopher.morrow@gmail.com; dkim=pass header.i=christopher.morrow@gmail.com
Received: from mr.google.com ([10.182.14.97]) by 10.182.14.97 with SMTP id o1mr8871539obc.57.1330997482750 (num_hops = 1); Mon, 05 Mar 2012 17:31:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=BWue4cCG6FuIdZJnMDt/7CXdMpRdAZim+Q5eE/YjEJA=; b=Wletv8bvSzVp177PFZrMUqfJBbSkjUII0pyVLiW0UQCrfW/z1cqgcSjU4hnyontc0x jleTje5/XgxJKw5jtb3mefXViWQdHzKIrt1jh9oLk46GtcUrBoOvZjKKknVT/2AdVov4 /Rskpcj31iPMLfkOBEZuhPP7UGEWuHvV5r5a6tnUqGu7rOJER6B6IZMKsO/y6/F93HOz ALRr8lE74FJNLXc8kaLOO0+KxXNSKgO3sTnW1WLmX91WmF53vskIO5041DNnvYMakLLA T7NHEFmh5dJFJQNuTO44NnGfxZQHdo/jT9sJUGbpGTpIP0qg4EwHEBmlX6eG0tPbX16H 7Yag==
MIME-Version: 1.0
Received: by 10.182.14.97 with SMTP id o1mr7802684obc.57.1330997482668; Mon, 05 Mar 2012 17:31:22 -0800 (PST)
Received: by 10.182.139.106 with HTTP; Mon, 5 Mar 2012 17:31:22 -0800 (PST)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D767D0BA53@EMBX01-WF.jnpr.net>
References: <20120228205159.11401.49917.idtracker@ietfa.amsl.com> <5F5784B7-4593-402E-A0E1-EB0047139B2E@secure64.com> <CAL9jLaYbu35EbxHuqB1RkGehuxY6kLNrtw_hOrNbaHkBAkURBA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D767D0BA53@EMBX01-WF.jnpr.net>
Date: Mon, 5 Mar 2012 20:31:22 -0500
Message-ID: <CAL9jLaYVL5b2cwTbnAFoAa5absDeWYURjvXEPQ5Jq_8hsQBDkA@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Ronald Bonica <rbonica@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 01:31:23 -0000

On Mon, Mar 5, 2012 at 8:12 PM, Ronald Bonica <rbonica@juniper.net> wrote:
> Chris,
>
> This draft appears to be operating in the same area as the origin authent=
ication work that is currently progressing in SIDR. Shouldn't all of that w=
ork be in one place?
>
> My guess is that it belongs in SIDR.

also was my guess, just looking for consensus on that I believe I was.

-chris

> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 Ron
>
>
>> -----Original Message-----
>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
>> Christopher Morrow
>> Sent: Monday, March 05, 2012 4:22 PM
>> To: Joseph Gersch
>> Cc: grow@ietf.org
>> Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-
>> grow-revdns-bgp-00.txt
>>
>> It would be helpful to the chairs (at least) to get a sense of the
>> 'room' (list) on this topic, it seems that the focus is really on a
>> dnsops sort of paper, though interaction could be had in the routing
>> space as well (or that's an intent of the draft's work).
>>
>> It's not clear that GROW is the place for this work, but keeping folks
>> informed isn't a bad plan either (I think).
>>
>> -chris
>> (co-chair)
>>
>> On Tue, Feb 28, 2012 at 3:58 PM, Joseph Gersch
>> <joe.gersch@secure64.com> wrote:
>> > All,
>> > =A0 we have submitted a new draft that we would like to present at the
>> > Paris IETF meeting.
>> > Please take the time to send any comments and suggestions regarding
>> > this idea on using records in =A0the reverse DNS to help secure BGP
>> route origins.
>> >
>> > Best regards,
>> > =A0 =A0- Joe Gersch, Dan Massey, Eric Osterweil and Lixia Zhang
>> >
>> > Begin forwarded message:
>> >
>> > From: internet-drafts@ietf.org
>> > Subject: New Version Notification for
>> > draft-gersch-grow-revdns-bgp-00.txt
>> > Date: February 28, 2012 1:51:59 PM MST
>> > To: joe.gersch@secure64.com
>> > Cc: lixia@cs.ucla.edu, eosterweil@verisign.com,
>> > massey@cs.colostate.edu
>> >
>> > A new version of I-D, draft-gersch-grow-revdns-bgp-00.txt has been
>> > successfully submitted by Joe Gersch and posted to the IETF
>> repository.
>> >
>> > Filename: draft-gersch-grow-revdns-bgp
>> > Revision: 00
>> > Title: DNS Resource Records for BGP Routing Data Creation date:
>> > 2012-02-29 WG ID: Individual Submission Number of pages: 22
>> >
>> > Abstract:
>> > =A0=A0This draft proposes the creation of two DNS record types for
>> storing
>> > =A0=A0BGP routing information in the reverse DNS. =A0The RLOCK record
>> allows
>> > =A0=A0prefix owners to indicate whether the DNS is being used to publi=
sh
>> > =A0=A0routing data. =A0The SRO record allows operators to indicate whe=
ther
>> > an
>> > =A0=A0IPv4 or IPv6 prefix ought to appear in global routing tables and
>> > =A0=A0identifies authorized origin Autonomous System Number(s) for tha=
t
>> > =A0=A0prefix. =A0The published data can be used in a variety of contex=
ts
>> and
>> > =A0=A0can be extended to include additional information. =A0This work =
is
>> > part
>> > =A0=A0of an on-going effort and is accessible in an active testbed.
>> >
>> >
>> >
>> >
>> > The IETF Secretariat
>> >
>> >
>> > Joseph Gersch
>> > Chief=A0Operating=A0Officer
>> > Secure64=A0Software=A0Corporation
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > GROW mailing list
>> > GROW@ietf.org
>> > https://www.ietf.org/mailman/listinfo/grow
>> >
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow

From terry.manderson@icann.org  Mon Mar  5 17:38:31 2012
Return-Path: <terry.manderson@icann.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EDCE21E806C for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 17:38:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.506
X-Spam-Level: 
X-Spam-Status: No, score=-106.506 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 rkBoHt0nlC96 for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 17:38:30 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by ietfa.amsl.com (Postfix) with ESMTP id B075021E8027 for <grow@ietf.org>; Mon,  5 Mar 2012 17:38:30 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Mon, 5 Mar 2012 17:38:30 -0800
From: Terry Manderson <terry.manderson@icann.org>
To: Christopher Morrow <christopher.morrow@gmail.com>, Ronald Bonica <rbonica@juniper.net>
Date: Mon, 5 Mar 2012 17:38:27 -0800
Thread-Topic: [GROW] Fwd: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
Thread-Index: Acz7OOZStfm58i37QOihqWohowMitQAAO1Yh
Message-ID: <CB7BA7B3.22721%terry.manderson@icann.org>
In-Reply-To: <CAL9jLaYVL5b2cwTbnAFoAa5absDeWYURjvXEPQ5Jq_8hsQBDkA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 01:38:31 -0000

>From my reading of the SIDR charter:

" Building upon the already completed and implemented framework:

* Resource Public Key Infrastructure (RPKI)
* Distribution of RPKI data to routing devices and its use in
operational networks
* Document the use of certification objects within the secure
routing architecture "

I didn't see any RPKI use mentioned in revdns-bgp.

So my guess is that if you went to present this at SIDR, most SIDR folk
would say "it doesn't use RPKI" this is not the place. Irrespective of how
flexible the chairs implement the charter under the allowances of the
responsible AD.

Cheers.
T.


On 6/03/12 11:31 AM, "Christopher Morrow" <christopher.morrow@gmail.com>
wrote:

> On Mon, Mar 5, 2012 at 8:12 PM, Ronald Bonica <rbonica@juniper.net> wrote=
:
>> Chris,
>>=20
>> This draft appears to be operating in the same area as the origin
>> authentication work that is currently progressing in SIDR. Shouldn't all=
 of
>> that work be in one place?
>>=20
>> My guess is that it belongs in SIDR.
>=20
> also was my guess, just looking for consensus on that I believe I was.
>=20
> -chris
>=20
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 Ron
>>=20
>>=20
>>> -----Original Message-----
>>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
>>> Christopher Morrow
>>> Sent: Monday, March 05, 2012 4:22 PM
>>> To: Joseph Gersch
>>> Cc: grow@ietf.org
>>> Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-
>>> grow-revdns-bgp-00.txt
>>>=20
>>> It would be helpful to the chairs (at least) to get a sense of the
>>> 'room' (list) on this topic, it seems that the focus is really on a
>>> dnsops sort of paper, though interaction could be had in the routing
>>> space as well (or that's an intent of the draft's work).
>>>=20
>>> It's not clear that GROW is the place for this work, but keeping folks
>>> informed isn't a bad plan either (I think).
>>>=20
>>> -chris
>>> (co-chair)
>>>=20
>>> On Tue, Feb 28, 2012 at 3:58 PM, Joseph Gersch
>>> <joe.gersch@secure64.com> wrote:
>>>> All,
>>>> =A0 we have submitted a new draft that we would like to present at the
>>>> Paris IETF meeting.
>>>> Please take the time to send any comments and suggestions regarding
>>>> this idea on using records in =A0the reverse DNS to help secure BGP
>>> route origins.
>>>>=20
>>>> Best regards,
>>>> =A0 =A0- Joe Gersch, Dan Massey, Eric Osterweil and Lixia Zhang
>>>>=20
>>>> Begin forwarded message:
>>>>=20
>>>> From: internet-drafts@ietf.org
>>>> Subject: New Version Notification for
>>>> draft-gersch-grow-revdns-bgp-00.txt
>>>> Date: February 28, 2012 1:51:59 PM MST
>>>> To: joe.gersch@secure64.com
>>>> Cc: lixia@cs.ucla.edu, eosterweil@verisign.com,
>>>> massey@cs.colostate.edu
>>>>=20
>>>> A new version of I-D, draft-gersch-grow-revdns-bgp-00.txt has been
>>>> successfully submitted by Joe Gersch and posted to the IETF
>>> repository.
>>>>=20
>>>> Filename: draft-gersch-grow-revdns-bgp
>>>> Revision: 00
>>>> Title: DNS Resource Records for BGP Routing Data Creation date:
>>>> 2012-02-29 WG ID: Individual Submission Number of pages: 22
>>>>=20
>>>> Abstract:
>>>> =A0=A0This draft proposes the creation of two DNS record types for
>>> storing
>>>> =A0=A0BGP routing information in the reverse DNS. =A0The RLOCK record
>>> allows
>>>> =A0=A0prefix owners to indicate whether the DNS is being used to publi=
sh
>>>> =A0=A0routing data. =A0The SRO record allows operators to indicate whe=
ther
>>>> an
>>>> =A0=A0IPv4 or IPv6 prefix ought to appear in global routing tables and
>>>> =A0=A0identifies authorized origin Autonomous System Number(s) for tha=
t
>>>> =A0=A0prefix. =A0The published data can be used in a variety of contex=
ts
>>> and
>>>> =A0=A0can be extended to include additional information. =A0This work =
is
>>>> part
>>>> =A0=A0of an on-going effort and is accessible in an active testbed.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> The IETF Secretariat
>>>>=20
>>>>=20
>>>> Joseph Gersch
>>>> Chief=A0Operating=A0Officer
>>>> Secure64=A0Software=A0Corporation
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> GROW mailing list
>>>> GROW@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/grow
>>>>=20
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From rbonica@juniper.net  Mon Mar  5 17:49:16 2012
Return-Path: <rbonica@juniper.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3595121E8024 for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 17:49:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.501
X-Spam-Level: 
X-Spam-Status: No, score=-106.501 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 nT-vQ-IFCRfr for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 17:49:15 -0800 (PST)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id B359021F851D for <grow@ietf.org>; Mon,  5 Mar 2012 17:48:53 -0800 (PST)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKT1VtBWtl6F5H+0/aqL5Xoxt0X9fwpAsz@postini.com; Mon, 05 Mar 2012 17:49:15 PST
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 5 Mar 2012 17:48:17 -0800
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Mon, 5 Mar 2012 20:48:17 -0500
From: Ronald Bonica <rbonica@juniper.net>
To: Terry Manderson <terry.manderson@icann.org>, Christopher Morrow <christopher.morrow@gmail.com>
Date: Mon, 5 Mar 2012 20:48:15 -0500
Thread-Topic: [GROW] Fwd: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
Thread-Index: Acz7OOZStfm58i37QOihqWohowMitQAAO1YhAABL04A=
Message-ID: <13205C286662DE4387D9AF3AC30EF456D767D0BA94@EMBX01-WF.jnpr.net>
References: <CAL9jLaYVL5b2cwTbnAFoAa5absDeWYURjvXEPQ5Jq_8hsQBDkA@mail.gmail.com> <CB7BA7B3.22721%terry.manderson@icann.org>
In-Reply-To: <CB7BA7B3.22721%terry.manderson@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 01:49:16 -0000

Is it attempting to solve a problem which is also being worked in SIDR?=20

                                                Ron

> -----Original Message-----
> From: Terry Manderson [mailto:terry.manderson@icann.org]
> Sent: Monday, March 05, 2012 8:38 PM
> To: Christopher Morrow; Ronald Bonica
> Cc: grow@ietf.org
> Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-
> grow-revdns-bgp-00.txt
>=20
> From my reading of the SIDR charter:
>=20
> " Building upon the already completed and implemented framework:
>=20
> * Resource Public Key Infrastructure (RPKI)
> * Distribution of RPKI data to routing devices and its use in
> operational networks
> * Document the use of certification objects within the secure routing
> architecture "
>=20
> I didn't see any RPKI use mentioned in revdns-bgp.
>=20
> So my guess is that if you went to present this at SIDR, most SIDR folk
> would say "it doesn't use RPKI" this is not the place. Irrespective of
> how flexible the chairs implement the charter under the allowances of
> the responsible AD.
>=20
> Cheers.
> T.
>=20
>=20
> On 6/03/12 11:31 AM, "Christopher Morrow"
> <christopher.morrow@gmail.com>
> wrote:
>=20
> > On Mon, Mar 5, 2012 at 8:12 PM, Ronald Bonica <rbonica@juniper.net>
> wrote:
> >> Chris,
> >>
> >> This draft appears to be operating in the same area as the origin
> >> authentication work that is currently progressing in SIDR. Shouldn't
> >> all of that work be in one place?
> >>
> >> My guess is that it belongs in SIDR.
> >
> > also was my guess, just looking for consensus on that I believe I
> was.
> >
> > -chris
> >
> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 Ron
> >>
> >>
> >>> -----Original Message-----
> >>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On
> Behalf
> >>> Of Christopher Morrow
> >>> Sent: Monday, March 05, 2012 4:22 PM
> >>> To: Joseph Gersch
> >>> Cc: grow@ietf.org
> >>> Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-
> >>> grow-revdns-bgp-00.txt
> >>>
> >>> It would be helpful to the chairs (at least) to get a sense of the
> >>> 'room' (list) on this topic, it seems that the focus is really on a
> >>> dnsops sort of paper, though interaction could be had in the
> routing
> >>> space as well (or that's an intent of the draft's work).
> >>>
> >>> It's not clear that GROW is the place for this work, but keeping
> >>> folks informed isn't a bad plan either (I think).
> >>>
> >>> -chris
> >>> (co-chair)
> >>>
> >>> On Tue, Feb 28, 2012 at 3:58 PM, Joseph Gersch
> >>> <joe.gersch@secure64.com> wrote:
> >>>> All,
> >>>> =A0 we have submitted a new draft that we would like to present at
> >>>> the Paris IETF meeting.
> >>>> Please take the time to send any comments and suggestions
> regarding
> >>>> this idea on using records in =A0the reverse DNS to help secure BGP
> >>> route origins.
> >>>>
> >>>> Best regards,
> >>>> =A0 =A0- Joe Gersch, Dan Massey, Eric Osterweil and Lixia Zhang
> >>>>
> >>>> Begin forwarded message:
> >>>>
> >>>> From: internet-drafts@ietf.org
> >>>> Subject: New Version Notification for
> >>>> draft-gersch-grow-revdns-bgp-00.txt
> >>>> Date: February 28, 2012 1:51:59 PM MST
> >>>> To: joe.gersch@secure64.com
> >>>> Cc: lixia@cs.ucla.edu, eosterweil@verisign.com,
> >>>> massey@cs.colostate.edu
> >>>>
> >>>> A new version of I-D, draft-gersch-grow-revdns-bgp-00.txt has been
> >>>> successfully submitted by Joe Gersch and posted to the IETF
> >>> repository.
> >>>>
> >>>> Filename: draft-gersch-grow-revdns-bgp
> >>>> Revision: 00
> >>>> Title: DNS Resource Records for BGP Routing Data Creation date:
> >>>> 2012-02-29 WG ID: Individual Submission Number of pages: 22
> >>>>
> >>>> Abstract:
> >>>> =A0=A0This draft proposes the creation of two DNS record types for
> >>> storing
> >>>> =A0=A0BGP routing information in the reverse DNS. =A0The RLOCK recor=
d
> >>> allows
> >>>> =A0=A0prefix owners to indicate whether the DNS is being used to
> >>>> publish
> >>>> =A0=A0routing data. =A0The SRO record allows operators to indicate
> >>>> whether an
> >>>> =A0=A0IPv4 or IPv6 prefix ought to appear in global routing tables a=
nd
> >>>> =A0=A0identifies authorized origin Autonomous System Number(s) for
> that
> >>>> =A0=A0prefix. =A0The published data can be used in a variety of cont=
exts
> >>> and
> >>>> =A0=A0can be extended to include additional information. =A0This wor=
k is
> >>>> part
> >>>> =A0=A0of an on-going effort and is accessible in an active testbed.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> The IETF Secretariat
> >>>>
> >>>>
> >>>> Joseph Gersch
> >>>> Chief=A0Operating=A0Officer
> >>>> Secure64=A0Software=A0Corporation
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> GROW mailing list
> >>>> GROW@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/grow
> >>>>
> >>> _______________________________________________
> >>> GROW mailing list
> >>> GROW@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/grow
> > _______________________________________________
> > GROW mailing list
> > GROW@ietf.org
> > https://www.ietf.org/mailman/listinfo/grow


From tony.li@tony.li  Mon Mar  5 18:00:00 2012
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4551121F8647 for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 18:00:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.439
X-Spam-Level: 
X-Spam-Status: No, score=-102.439 tagged_above=-999 required=5 tests=[AWL=0.160, 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 P6UPmvvdYD+l for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 17:59:59 -0800 (PST)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by ietfa.amsl.com (Postfix) with ESMTP id 5B9E821F8642 for <grow@ietf.org>; Mon,  5 Mar 2012 17:59:59 -0800 (PST)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta04.westchester.pa.mail.comcast.net with comcast id i1yW1i00927AodY541zzFU; Tue, 06 Mar 2012 01:59:59 +0000
Received: from [10.155.34.217] ([128.107.239.233]) by omta19.westchester.pa.mail.comcast.net with comcast id i1zj1i00h52qHCY3f1zm60; Tue, 06 Mar 2012 01:59:57 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Tony Li <tony.li@tony.li>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D767D0BA94@EMBX01-WF.jnpr.net>
Date: Mon, 5 Mar 2012 17:59:42 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <FCCAEEC2-2D47-47BF-AC34-8EDCE51F805F@tony.li>
References: <CAL9jLaYVL5b2cwTbnAFoAa5absDeWYURjvXEPQ5Jq_8hsQBDkA@mail.gmail.com> <CB7BA7B3.22721%terry.manderson@icann.org> <13205C286662DE4387D9AF3AC30EF456D767D0BA94@EMBX01-WF.jnpr.net>
To: Ronald Bonica <rbonica@juniper.net>
X-Mailer: Apple Mail (2.1257)
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 02:00:00 -0000

Not to mention we rejected this idea long ago, in favor of working on SIDR.

It's dead, Jim.

Tony


On Mar 5, 2012, at 5:48 PM, Ronald Bonica wrote:

> Is it attempting to solve a problem which is also being worked in SIDR? 
> 
>                                                Ron
> 
>> -----Original Message-----
>> From: Terry Manderson [mailto:terry.manderson@icann.org]
>> Sent: Monday, March 05, 2012 8:38 PM
>> To: Christopher Morrow; Ronald Bonica
>> Cc: grow@ietf.org
>> Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-
>> grow-revdns-bgp-00.txt
>> 
>> From my reading of the SIDR charter:
>> 
>> " Building upon the already completed and implemented framework:
>> 
>> * Resource Public Key Infrastructure (RPKI)
>> * Distribution of RPKI data to routing devices and its use in
>> operational networks
>> * Document the use of certification objects within the secure routing
>> architecture "
>> 
>> I didn't see any RPKI use mentioned in revdns-bgp.
>> 
>> So my guess is that if you went to present this at SIDR, most SIDR folk
>> would say "it doesn't use RPKI" this is not the place. Irrespective of
>> how flexible the chairs implement the charter under the allowances of
>> the responsible AD.
>> 
>> Cheers.
>> T.
>> 
>> 
>> On 6/03/12 11:31 AM, "Christopher Morrow"
>> <christopher.morrow@gmail.com>
>> wrote:
>> 
>>> On Mon, Mar 5, 2012 at 8:12 PM, Ronald Bonica <rbonica@juniper.net>
>> wrote:
>>>> Chris,
>>>> 
>>>> This draft appears to be operating in the same area as the origin
>>>> authentication work that is currently progressing in SIDR. Shouldn't
>>>> all of that work be in one place?
>>>> 
>>>> My guess is that it belongs in SIDR.
>>> 
>>> also was my guess, just looking for consensus on that I believe I
>> was.
>>> 
>>> -chris
>>> 
>>>>                                                 Ron
>>>> 
>>>> 
>>>>> -----Original Message-----
>>>>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On
>> Behalf
>>>>> Of Christopher Morrow
>>>>> Sent: Monday, March 05, 2012 4:22 PM
>>>>> To: Joseph Gersch
>>>>> Cc: grow@ietf.org
>>>>> Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-
>>>>> grow-revdns-bgp-00.txt
>>>>> 
>>>>> It would be helpful to the chairs (at least) to get a sense of the
>>>>> 'room' (list) on this topic, it seems that the focus is really on a
>>>>> dnsops sort of paper, though interaction could be had in the
>> routing
>>>>> space as well (or that's an intent of the draft's work).
>>>>> 
>>>>> It's not clear that GROW is the place for this work, but keeping
>>>>> folks informed isn't a bad plan either (I think).
>>>>> 
>>>>> -chris
>>>>> (co-chair)
>>>>> 
>>>>> On Tue, Feb 28, 2012 at 3:58 PM, Joseph Gersch
>>>>> <joe.gersch@secure64.com> wrote:
>>>>>> All,
>>>>>>   we have submitted a new draft that we would like to present at
>>>>>> the Paris IETF meeting.
>>>>>> Please take the time to send any comments and suggestions
>> regarding
>>>>>> this idea on using records in  the reverse DNS to help secure BGP
>>>>> route origins.
>>>>>> 
>>>>>> Best regards,
>>>>>>    - Joe Gersch, Dan Massey, Eric Osterweil and Lixia Zhang
>>>>>> 
>>>>>> Begin forwarded message:
>>>>>> 
>>>>>> From: internet-drafts@ietf.org
>>>>>> Subject: New Version Notification for
>>>>>> draft-gersch-grow-revdns-bgp-00.txt
>>>>>> Date: February 28, 2012 1:51:59 PM MST
>>>>>> To: joe.gersch@secure64.com
>>>>>> Cc: lixia@cs.ucla.edu, eosterweil@verisign.com,
>>>>>> massey@cs.colostate.edu
>>>>>> 
>>>>>> A new version of I-D, draft-gersch-grow-revdns-bgp-00.txt has been
>>>>>> successfully submitted by Joe Gersch and posted to the IETF
>>>>> repository.
>>>>>> 
>>>>>> Filename: draft-gersch-grow-revdns-bgp
>>>>>> Revision: 00
>>>>>> Title: DNS Resource Records for BGP Routing Data Creation date:
>>>>>> 2012-02-29 WG ID: Individual Submission Number of pages: 22
>>>>>> 
>>>>>> Abstract:
>>>>>>   This draft proposes the creation of two DNS record types for
>>>>> storing
>>>>>>   BGP routing information in the reverse DNS.  The RLOCK record
>>>>> allows
>>>>>>   prefix owners to indicate whether the DNS is being used to
>>>>>> publish
>>>>>>   routing data.  The SRO record allows operators to indicate
>>>>>> whether an
>>>>>>   IPv4 or IPv6 prefix ought to appear in global routing tables and
>>>>>>   identifies authorized origin Autonomous System Number(s) for
>> that
>>>>>>   prefix.  The published data can be used in a variety of contexts
>>>>> and
>>>>>>   can be extended to include additional information.  This work is
>>>>>> part
>>>>>>   of an on-going effort and is accessible in an active testbed.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> The IETF Secretariat
>>>>>> 
>>>>>> 
>>>>>> Joseph Gersch
>>>>>> Chief Operating Officer
>>>>>> Secure64 Software Corporation
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> GROW mailing list
>>>>>> GROW@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/grow
>>>>>> 
>>>>> _______________________________________________
>>>>> GROW mailing list
>>>>> GROW@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/grow
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
> 
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From terry.manderson@icann.org  Mon Mar  5 18:08:36 2012
Return-Path: <terry.manderson@icann.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D0B721E8027 for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 18:08:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.512
X-Spam-Level: 
X-Spam-Status: No, score=-106.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 sFy8ZIqaKlUg for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 18:08:35 -0800 (PST)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by ietfa.amsl.com (Postfix) with ESMTP id C7E8321E8018 for <grow@ietf.org>; Mon,  5 Mar 2012 18:08:35 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Mon, 5 Mar 2012 18:08:35 -0800
From: Terry Manderson <terry.manderson@icann.org>
To: Ronald Bonica <rbonica@juniper.net>, Christopher Morrow <christopher.morrow@gmail.com>
Date: Mon, 5 Mar 2012 18:08:30 -0800
Thread-Topic: [GROW] Fwd: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
Thread-Index: Acz7OOZStfm58i37QOihqWohowMitQAAO1YhAABL04AAAMDYpw==
Message-ID: <CB7BAEBE.2272B%terry.manderson@icann.org>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D767D0BA94@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 02:08:36 -0000

from the draft in question:

" We limit the scope of this internet draft to the prevention of origin
   and sub-prefix hijacks -- a capability that can be implemented and
   deployed in a reasonable time frame."

I think SIDR has completed its work on this item.

This looks to me like a fresh set of eyes on the problem.

I'd be willing, if there is time on the grow agenda, to listen to what the
authors are proposing and then reflect on the GROW v SIDR question.

You may be right - it may be a SIDR item. But given the SIDR space right no=
w
seems to be focused on the interaction with and between routers I'm not sur=
e
presenting it in SIDR will be be good for either SIDR or the Authors.
 .. just saying is all..

Cheers
Terry


On 6/03/12 11:48 AM, "Ronald Bonica" <rbonica@juniper.net> wrote:

> Is it attempting to solve a problem which is also being worked in SIDR?
>=20
>                                                 Ron
>=20
>> -----Original Message-----
>> From: Terry Manderson [mailto:terry.manderson@icann.org]
>> Sent: Monday, March 05, 2012 8:38 PM
>> To: Christopher Morrow; Ronald Bonica
>> Cc: grow@ietf.org
>> Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-
>> grow-revdns-bgp-00.txt
>>=20
>> From my reading of the SIDR charter:
>>=20
>> " Building upon the already completed and implemented framework:
>>=20
>> * Resource Public Key Infrastructure (RPKI)
>> * Distribution of RPKI data to routing devices and its use in
>> operational networks
>> * Document the use of certification objects within the secure routing
>> architecture "
>>=20
>> I didn't see any RPKI use mentioned in revdns-bgp.
>>=20
>> So my guess is that if you went to present this at SIDR, most SIDR folk
>> would say "it doesn't use RPKI" this is not the place. Irrespective of
>> how flexible the chairs implement the charter under the allowances of
>> the responsible AD.
>>=20
>> Cheers.
>> T.
>>=20
>>=20
>> On 6/03/12 11:31 AM, "Christopher Morrow"
>> <christopher.morrow@gmail.com>
>> wrote:
>>=20
>>> On Mon, Mar 5, 2012 at 8:12 PM, Ronald Bonica <rbonica@juniper.net>
>> wrote:
>>>> Chris,
>>>>=20
>>>> This draft appears to be operating in the same area as the origin
>>>> authentication work that is currently progressing in SIDR. Shouldn't
>>>> all of that work be in one place?
>>>>=20
>>>> My guess is that it belongs in SIDR.
>>>=20
>>> also was my guess, just looking for consensus on that I believe I
>> was.
>>>=20
>>> -chris
>>>=20
>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 Ron
>>>>=20
>>>>=20
>>>>> -----Original Message-----
>>>>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On
>> Behalf
>>>>> Of Christopher Morrow
>>>>> Sent: Monday, March 05, 2012 4:22 PM
>>>>> To: Joseph Gersch
>>>>> Cc: grow@ietf.org
>>>>> Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-
>>>>> grow-revdns-bgp-00.txt
>>>>>=20
>>>>> It would be helpful to the chairs (at least) to get a sense of the
>>>>> 'room' (list) on this topic, it seems that the focus is really on a
>>>>> dnsops sort of paper, though interaction could be had in the
>> routing
>>>>> space as well (or that's an intent of the draft's work).
>>>>>=20
>>>>> It's not clear that GROW is the place for this work, but keeping
>>>>> folks informed isn't a bad plan either (I think).
>>>>>=20
>>>>> -chris
>>>>> (co-chair)
>>>>>=20
>>>>> On Tue, Feb 28, 2012 at 3:58 PM, Joseph Gersch
>>>>> <joe.gersch@secure64.com> wrote:
>>>>>> All,
>>>>>> =A0 we have submitted a new draft that we would like to present at
>>>>>> the Paris IETF meeting.
>>>>>> Please take the time to send any comments and suggestions
>> regarding
>>>>>> this idea on using records in =A0the reverse DNS to help secure BGP
>>>>> route origins.
>>>>>>=20
>>>>>> Best regards,
>>>>>> =A0 =A0- Joe Gersch, Dan Massey, Eric Osterweil and Lixia Zhang
>>>>>>=20
>>>>>> Begin forwarded message:
>>>>>>=20
>>>>>> From: internet-drafts@ietf.org
>>>>>> Subject: New Version Notification for
>>>>>> draft-gersch-grow-revdns-bgp-00.txt
>>>>>> Date: February 28, 2012 1:51:59 PM MST
>>>>>> To: joe.gersch@secure64.com
>>>>>> Cc: lixia@cs.ucla.edu, eosterweil@verisign.com,
>>>>>> massey@cs.colostate.edu
>>>>>>=20
>>>>>> A new version of I-D, draft-gersch-grow-revdns-bgp-00.txt has been
>>>>>> successfully submitted by Joe Gersch and posted to the IETF
>>>>> repository.
>>>>>>=20
>>>>>> Filename: draft-gersch-grow-revdns-bgp
>>>>>> Revision: 00
>>>>>> Title: DNS Resource Records for BGP Routing Data Creation date:
>>>>>> 2012-02-29 WG ID: Individual Submission Number of pages: 22
>>>>>>=20
>>>>>> Abstract:
>>>>>> =A0=A0This draft proposes the creation of two DNS record types for
>>>>> storing
>>>>>> =A0=A0BGP routing information in the reverse DNS. =A0The RLOCK recor=
d
>>>>> allows
>>>>>> =A0=A0prefix owners to indicate whether the DNS is being used to
>>>>>> publish
>>>>>> =A0=A0routing data. =A0The SRO record allows operators to indicate
>>>>>> whether an
>>>>>> =A0=A0IPv4 or IPv6 prefix ought to appear in global routing tables a=
nd
>>>>>> =A0=A0identifies authorized origin Autonomous System Number(s) for
>> that
>>>>>> =A0=A0prefix. =A0The published data can be used in a variety of cont=
exts
>>>>> and
>>>>>> =A0=A0can be extended to include additional information. =A0This wor=
k is
>>>>>> part
>>>>>> =A0=A0of an on-going effort and is accessible in an active testbed.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> The IETF Secretariat
>>>>>>=20
>>>>>>=20
>>>>>> Joseph Gersch
>>>>>> Chief=A0Operating=A0Officer
>>>>>> Secure64=A0Software=A0Corporation
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> GROW mailing list
>>>>>> GROW@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/grow
>>>>>>=20
>>>>> _______________________________________________
>>>>> GROW mailing list
>>>>> GROW@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/grow
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
>=20


From robert@raszuk.net  Mon Mar  5 18:19:55 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D09821E8074 for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 18:19:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
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 eQnu3OmxG75x for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 18:19:54 -0800 (PST)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 5F55121E807E for <grow@ietf.org>; Mon,  5 Mar 2012 18:19:54 -0800 (PST)
Received: (qmail 6752 invoked by uid 399); 6 Mar 2012 02:19:53 -0000
Received: from unknown (HELO ?216.69.69.231?) (pbs:robert@raszuk.net@216.69.69.231) by mail1310.opentransfer.com with ESMTPM; 6 Mar 2012 02:19:53 -0000
X-Originating-IP: 216.69.69.231
Message-ID: <4F557449.4050702@raszuk.net>
Date: Tue, 06 Mar 2012 03:19:53 +0100
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Tony Li <tony.li@tony.li>
References: <CAL9jLaYVL5b2cwTbnAFoAa5absDeWYURjvXEPQ5Jq_8hsQBDkA@mail.gmail.com> <CB7BA7B3.22721%terry.manderson@icann.org> <13205C286662DE4387D9AF3AC30EF456D767D0BA94@EMBX01-WF.jnpr.net> <FCCAEEC2-2D47-47BF-AC34-8EDCE51F805F@tony.li>
In-Reply-To: <FCCAEEC2-2D47-47BF-AC34-8EDCE51F805F@tony.li>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 02:19:55 -0000

Hi Tony,

> Not to mention we rejected this idea long ago, in favor of working on SIDR.

Would you happen to have a pointer to the list discussions on this ? Did 
that included DNSSEC at that time ?

I agree with Terry here that this is just a fresh look at the problem 
space. If SIDR is mandated by the charter to be based on RPKI this 
clearly does not belong there. It seems like this is a new operational 
tool which GROW WG may be a good fit for.

I would support to get this presented in GROW if there is room in the 
agenda.

Rgs,
R.





From tony.li@tony.li  Mon Mar  5 18:28:53 2012
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6025421E8081 for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 18:28:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.454
X-Spam-Level: 
X-Spam-Status: No, score=-102.454 tagged_above=-999 required=5 tests=[AWL=0.145, 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 LmH7YV1u4N21 for <grow@ietfa.amsl.com>; Mon,  5 Mar 2012 18:28:52 -0800 (PST)
Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by ietfa.amsl.com (Postfix) with ESMTP id 8E61D21E8072 for <grow@ietf.org>; Mon,  5 Mar 2012 18:28:52 -0800 (PST)
Received: from omta04.emeryville.ca.mail.comcast.net ([76.96.30.35]) by qmta06.emeryville.ca.mail.comcast.net with comcast id i2Sx1i0060lTkoCA62UsDa; Tue, 06 Mar 2012 02:28:52 +0000
Received: from [10.155.34.217] ([128.107.239.233]) by omta04.emeryville.ca.mail.comcast.net with comcast id i2Uh1i00b52qHCY8Q2UjWz; Tue, 06 Mar 2012 02:28:50 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Tony Li <tony.li@tony.li>
In-Reply-To: <4F557449.4050702@raszuk.net>
Date: Mon, 5 Mar 2012 18:28:41 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <11D4D6E5-B675-42F7-B0E0-314B1F5002EB@tony.li>
References: <CAL9jLaYVL5b2cwTbnAFoAa5absDeWYURjvXEPQ5Jq_8hsQBDkA@mail.gmail.com> <CB7BA7B3.22721%terry.manderson@icann.org> <13205C286662DE4387D9AF3AC30EF456D767D0BA94@EMBX01-WF.jnpr.net> <FCCAEEC2-2D47-47BF-AC34-8EDCE51F805F@tony.li> <4F557449.4050702@raszuk.net>
To: robert@raszuk.net
X-Mailer: Apple Mail (2.1257)
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 02:28:53 -0000

Hi Robert,

> Would you happen to have a pointer to the list discussions on this ? =
Did that included DNSSEC at that time ?


This was an NDSS discussion at the time.  Same community tho.  Yes, it =
included DNSSEC.

http://www.isoc.org/isoc/conferences/ndss/99/proceedings/slides/li.pdf

Tony


From arturo.servin@gmail.com  Tue Mar  6 02:49:32 2012
Return-Path: <arturo.servin@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D712121F8878 for <grow@ietfa.amsl.com>; Tue,  6 Mar 2012 02:49:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 LTl9+s7gaUjY for <grow@ietfa.amsl.com>; Tue,  6 Mar 2012 02:49:32 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id C227D21F8875 for <grow@ietf.org>; Tue,  6 Mar 2012 02:49:31 -0800 (PST)
Received: by vcbfk13 with SMTP id fk13so4933111vcb.31 for <grow@ietf.org>; Tue, 06 Mar 2012 02:49:31 -0800 (PST)
Received-SPF: pass (google.com: domain of arturo.servin@gmail.com designates 10.52.179.102 as permitted sender) client-ip=10.52.179.102; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of arturo.servin@gmail.com designates 10.52.179.102 as permitted sender) smtp.mail=arturo.servin@gmail.com; dkim=pass header.i=arturo.servin@gmail.com
Received: from mr.google.com ([10.52.179.102]) by 10.52.179.102 with SMTP id df6mr41701469vdc.28.1331030971407 (num_hops = 1); Tue, 06 Mar 2012 02:49:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=IwSM+bpqz5oF9Q39gPH4UhAGAv3If9RnA9ZUi+S/d80=; b=g00ZnwqaDn8ApDe3UvtTY+rmExrI6R+sR7W62Akkuk6qzuxBQxDy4QDdV4c4Ix7AYb AiLEMcUhbHEqVic3N9WtFsF651pqtMFGdj9E/P3n5YBCBZGvnUmylPzKoRnFDQenrtuB A1LqEGBfgXZ2SoE6lMOZJnFMUJW3SU2bAWcCW5+a32xJsOxMDffSVIizi8vWdnXRPi0Z tGlIW/rU4ETqkmBbuLP+vkGzggXH7k+W6HeJVbYMjdgtPqVb69SsEfpv1hKlt7CLCCbq Tm1O62GaKPbutg0Q0gU7kq4tg+INPPRuHpZDxQ3y+C2KbYlnmBtKi9HA0QL2IEpL6z6R MaXQ==
Received: by 10.52.179.102 with SMTP id df6mr35575684vdc.28.1331030971168; Tue, 06 Mar 2012 02:49:31 -0800 (PST)
Received: from [192.168.1.103] (r186-48-206-158.dialup.adsl.anteldata.net.uy. [186.48.206.158]) by mx.google.com with ESMTPS id d7sm30051175vdu.15.2012.03.06.02.49.28 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 06 Mar 2012 02:49:30 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Arturo Servin <arturo.servin@gmail.com>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D767D0BA53@EMBX01-WF.jnpr.net>
Date: Tue, 6 Mar 2012 08:49:25 -0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DBDAF5A4-648F-42F6-92C9-505186916CA3@gmail.com>
References: <20120228205159.11401.49917.idtracker@ietfa.amsl.com> <5F5784B7-4593-402E-A0E1-EB0047139B2E@secure64.com> <CAL9jLaYbu35EbxHuqB1RkGehuxY6kLNrtw_hOrNbaHkBAkURBA@mail.gmail.com> <13205C286662DE4387D9AF3AC30EF456D767D0BA53@EMBX01-WF.jnpr.net>
To: Ronald Bonica <rbonica@juniper.net>, Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: grow@ietf.org
Subject: Re: [GROW] Fwd: New Version Notification for	draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 10:49:32 -0000

Chris, Ron

	I do not think that grow is the best place for this work. I =
agree that SIDR does not consider it in its current charter, but I do =
not see any other WG where this work should be.

	Perhaps, trying to re-charter SIDR to inclue this work? Yes, it =
may be hard but I think we need to work on this in SIDR to have =
complementary and aligned solutions with the current work on RPKI, =
origin-validation and BGPSEC.

Regards,
/as

On 5 Mar 2012, at 23:12, Ronald Bonica wrote:

> Chris,
>=20
> This draft appears to be operating in the same area as the origin =
authentication work that is currently progressing in SIDR. Shouldn't all =
of that work be in one place?
>=20
> My guess is that it belongs in SIDR.
>=20
>                                                 Ron
>=20
>=20
>> -----Original Message-----
>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf =
Of
>> Christopher Morrow
>> Sent: Monday, March 05, 2012 4:22 PM
>> To: Joseph Gersch
>> Cc: grow@ietf.org
>> Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-
>> grow-revdns-bgp-00.txt
>>=20
>> It would be helpful to the chairs (at least) to get a sense of the
>> 'room' (list) on this topic, it seems that the focus is really on a
>> dnsops sort of paper, though interaction could be had in the routing
>> space as well (or that's an intent of the draft's work).
>>=20
>> It's not clear that GROW is the place for this work, but keeping =
folks
>> informed isn't a bad plan either (I think).
>>=20
>> -chris
>> (co-chair)
>>=20
>> On Tue, Feb 28, 2012 at 3:58 PM, Joseph Gersch
>> <joe.gersch@secure64.com> wrote:
>>> All,
>>>   we have submitted a new draft that we would like to present at the
>>> Paris IETF meeting.
>>> Please take the time to send any comments and suggestions regarding
>>> this idea on using records in  the reverse DNS to help secure BGP
>> route origins.
>>>=20
>>> Best regards,
>>>    - Joe Gersch, Dan Massey, Eric Osterweil and Lixia Zhang
>>>=20
>>> Begin forwarded message:
>>>=20
>>> From: internet-drafts@ietf.org
>>> Subject: New Version Notification for
>>> draft-gersch-grow-revdns-bgp-00.txt
>>> Date: February 28, 2012 1:51:59 PM MST
>>> To: joe.gersch@secure64.com
>>> Cc: lixia@cs.ucla.edu, eosterweil@verisign.com,
>>> massey@cs.colostate.edu
>>>=20
>>> A new version of I-D, draft-gersch-grow-revdns-bgp-00.txt has been
>>> successfully submitted by Joe Gersch and posted to the IETF
>> repository.
>>>=20
>>> Filename: draft-gersch-grow-revdns-bgp
>>> Revision: 00
>>> Title: DNS Resource Records for BGP Routing Data Creation date:
>>> 2012-02-29 WG ID: Individual Submission Number of pages: 22
>>>=20
>>> Abstract:
>>>   This draft proposes the creation of two DNS record types for
>> storing
>>>   BGP routing information in the reverse DNS.  The RLOCK record
>> allows
>>>   prefix owners to indicate whether the DNS is being used to publish
>>>   routing data.  The SRO record allows operators to indicate whether
>>> an
>>>   IPv4 or IPv6 prefix ought to appear in global routing tables and
>>>   identifies authorized origin Autonomous System Number(s) for that
>>>   prefix.  The published data can be used in a variety of contexts
>> and
>>>   can be extended to include additional information.  This work is
>>> part
>>>   of an on-going effort and is accessible in an active testbed.
>>>=20
>>>=20
>>>=20
>>>=20
>>> The IETF Secretariat
>>>=20
>>>=20
>>> Joseph Gersch
>>> Chief Operating Officer
>>> Secure64 Software Corporation
>>>=20
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
>>>=20
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


From roland.dobbins@gmail.com  Wed Mar  7 04:52:17 2012
Return-Path: <roland.dobbins@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D536D21F8677 for <grow@ietfa.amsl.com>; Wed,  7 Mar 2012 04:52:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 s3yeTvg4q66v for <grow@ietfa.amsl.com>; Wed,  7 Mar 2012 04:52:17 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC4F21F8663 for <grow@ietf.org>; Wed,  7 Mar 2012 04:52:17 -0800 (PST)
Received: by yenm5 with SMTP id m5so3170371yen.31 for <grow@ietf.org>; Wed, 07 Mar 2012 04:52:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=1ZFf7R9I2gmyfUEPzF6I+djZ0j2uyuvFW+DTc9NelAE=; b=eUC5Irwy75G2penm+Ol010elvI/GQk26axpsHmtmT3KwQDv36FuXsjourRAtxJOnP7 VYqvxg3yYBmd9rRH50v40cdQRwSxmSJi2J4PFPXkf9wiSauyIWRif1vZ5nTB90H/xeh4 70NpC0w54h6FPYszwSElOGnKJq7dq7nbYO0jronG/rSWpynM98C3qK/EGaW+YNsHi9Cd 0kUTGPi6Qyj1XAdC/GSgxxuuhlNg81gwAPWgduEJ0TKF9+tkHcsbRJ0DLGGP2QPdyFd4 Sl99jWwn3JyWsc8rBTbbK8eFFalvY4OFAOmLrC2lgjNqCYBaDs3nODDy+ar2bvXLtfeo W3tQ==
Received: by 10.50.10.198 with SMTP id k6mr1805114igb.3.1331124736772; Wed, 07 Mar 2012 04:52:16 -0800 (PST)
Received: from [172.16.1.3] ([210.19.132.193]) by mx.google.com with ESMTPS id ko6sm12324866igc.2.2012.03.07.04.52.14 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 07 Mar 2012 04:52:15 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1257)
From: Roland Dobbins <roland.dobbins@gmail.com>
In-Reply-To: <FCCAEEC2-2D47-47BF-AC34-8EDCE51F805F@tony.li>
Date: Wed, 7 Mar 2012 19:52:11 +0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <29259701-8DA1-4F31-86CB-12E1632974BC@gmail.com>
References: <CAL9jLaYVL5b2cwTbnAFoAa5absDeWYURjvXEPQ5Jq_8hsQBDkA@mail.gmail.com> <CB7BA7B3.22721%terry.manderson@icann.org> <13205C286662DE4387D9AF3AC30EF456D767D0BA94@EMBX01-WF.jnpr.net> <FCCAEEC2-2D47-47BF-AC34-8EDCE51F805F@tony.li>
To: "grow@ietf.org grow@ietf.org" <grow@ietf.org>
X-Mailer: Apple Mail (2.1257)
Subject: Re: [GROW] New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 12:52:18 -0000

On Mar 6, 2012, at 8:59 AM, Tony Li wrote:

> Not to mention we rejected this idea long ago, in favor of working on =
SIDR.

FWIW, I view using the DNS for this sort of thing as both a) =
essentially, a recursive dependency and b) a layering violation, and it =
should be avoided on either one of those grounds.=

From tkirkham@anthony-kirkham.com  Wed Mar  7 13:26:21 2012
Return-Path: <tkirkham@anthony-kirkham.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4904311E80A1 for <grow@ietfa.amsl.com>; Wed,  7 Mar 2012 13:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 88JMn15nU5Fu for <grow@ietfa.amsl.com>; Wed,  7 Mar 2012 13:26:17 -0800 (PST)
Received: from nskntmtas04p.mx.bigpond.com (nskntmtas04p.mx.bigpond.com [61.9.168.146]) by ietfa.amsl.com (Postfix) with ESMTP id 3650311E809A for <grow@ietf.org>; Wed,  7 Mar 2012 13:26:16 -0800 (PST)
Received: from nskntotgx04p.mx.bigpond.com ([124.187.92.14]) by nskntmtas04p.mx.bigpond.com with ESMTP id <20120307212615.OVCR6123.nskntmtas04p.mx.bigpond.com@nskntotgx04p.mx.bigpond.com> for <grow@ietf.org>; Wed, 7 Mar 2012 21:26:15 +0000
Received: from Anthonys-MacBook-Pro.local ([124.187.92.14]) by nskntotgx04p.mx.bigpond.com with ESMTP id <20120307212613.TYBU1840.nskntotgx04p.mx.bigpond.com@Anthonys-MacBook-Pro.local> for <grow@ietf.org>; Wed, 7 Mar 2012 21:26:13 +0000
Message-ID: <4F57D274.5000802@anthony-kirkham.com>
Date: Thu, 08 Mar 2012 07:26:12 +1000
From: Anthony Kirkham <tkirkham@anthony-kirkham.com>
Organization: Anthony-Kirkham.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "grow@ietf.org" <grow@ietf.org>
Content-Type: multipart/mixed; boundary="------------010106000702080907090302"
X-Authentication-Info: Submitted using SMTP AUTH PLAIN at nskntotgx04p.mx.bigpond.com from [124.187.92.14] using ID anthony.kirkham at Wed, 7 Mar 2012 21:26:12 +0000
X-SIH-MSG-ID: rx46FNT4TFGqgDwlhSz7al42mVS1/AF5uMhSBI0wt0lHEVbCu8XAQsKkbapD34/ixFkZYgr4byMwc6v0X47bsN+6ILlBWLDY5cI=
Subject: [GROW] draft-ietf-grow-private-ip-sp-cores-00
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tkirkham@anthony-kirkham.com
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 21:26:21 -0000

This is a multi-part message in MIME format.
--------------010106000702080907090302
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

All,

To cut a long story short, I had uploaded this draft through datatracker 
two moths back. For some reason it never seemed to have been posted. The 
material in this draft is essentially identical to the last individual 
submission I put forward. Since we are now in a blackout period, I will 
send (a re-dated version of 00) to the list. I believe this should be at 
last call status.

Regards
Tony K

-- 



--------------010106000702080907090302
Content-Type: text/plain;
 name="draft-ietf-grow-private-ip-sp-cores-00.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="draft-ietf-grow-private-ip-sp-cores-00.txt"




Network Working Group                                         A. Kirkham
Internet-Draft                                        Palo Alto Networks
Obsoletes:  None (if approved)                             March 5, 2012
Intended status:  Informational
Expires:  September 6, 2012


           Issues with Private IP Addressing in the Internet
                 draft-ietf-grow-private-ip-sp-cores-00

Abstract

   The purpose of this document is to provide a discussion of the
   potential problems of using private, RFC1918, or non-globally-
   routable addressing within the core of an SP network.  The discussion
   focuses on link addresses and to a small extent loopback addresses.
   While many of the issues are well recognised within the ISP
   community, there appears to be no document that collectively
   describes the issues.

Legal

   This documents and the information contained therein are provided on
   an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
   REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
   IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
   WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
   WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
   ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
   FOR A PARTICULAR PURPOSE.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 6, 2012.




Kirkham                 Expires September 6, 2012               [Page 1]

Internet-Draft             private-ip-sp-cores                March 2012


Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Conservation of Address Space  . . . . . . . . . . . . . . . .  3
   3.  Effects on Traceroute  . . . . . . . . . . . . . . . . . . . .  4
   4.  Effects on Path MTU Discovery  . . . . . . . . . . . . . . . .  7
   5.  Unexpected interactions with some NAT implementations  . . . .  8
   6.  Interactions with edge anti-spoofing techniques  . . . . . . . 10
   7.  Peering using loopbacks  . . . . . . . . . . . . . . . . . . . 11
   8.  DNS Interaction  . . . . . . . . . . . . . . . . . . . . . . . 11
   9.  Operational and Troubleshooting issues . . . . . . . . . . . . 11
   10. Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   11. Alternate approaches to core network security  . . . . . . . . 13
   12. Normative References . . . . . . . . . . . . . . . . . . . . . 14
   Appendix A.  Acknowledgments . . . . . . . . . . . . . . . . . . . 14
   Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 15


















Kirkham                 Expires September 6, 2012               [Page 2]

Internet-Draft             private-ip-sp-cores                March 2012


1.  Introduction

   In the mid to late 90's, some Internet Service Providers (ISPs)
   adopted the practice of utilising private (or non-globally unique) IP
   (i.e.  RFC1918) addresses for the infrastructure links and in some
   cases the loopback interfaces within their networks.  The reasons for
   this approach centered on conservation of address space (i.e.
   scarcity of public IPv4 address space), and security of the core
   network (also known as core hiding).

   However, a number of technical and operational issues occurred as a
   result of using private (or non-globally unique) IP addresses, and
   virtually all these ISPs moved away from the practice.  Tier 1 ISPs
   are considered the benchmark of the industry and as of the time of
   writing, there is no known tier 1 ISP that utilises the practice of
   private addressing within their core network.

   The following sections will discuss the various issues associated
   with deploying private IP (i.e.  RFC1918) addresses within ISP core
   networks.

   The intent of this document is not to suggest that private IP can not
   be used with the core of an SP network as some providers use this
   practice and operate successfully.  The intent is to outline the
   potential issues or effects of such a practice.

   Note:  The practice of ISPs using 'stolen' address space (also known
   as 'squat' space) has many of the same issues (or effects) as that of
   using private IP address space within core networks.  The term
   "stolen IP address space" refers to the practice of an ISP using
   address space for its own infrastructure/core network addressing that
   has been officially allocated by an RIR to another provider, but that
   provider is not currently using or advertising within the Internet.
   Stolen addressing is not discussed further in this document.  It is
   simply noted as an associated issue.


2.  Conservation of Address Space

   One of the original intents for the use of private IP addressing
   within an ISP core was the conservation of IP address space.  When an
   ISP is allocated a block of public IP addresses (from a RIR), this
   address block was traditionally split in order to dedicate some
   portion for infrastructure use (i.e. for the core network), and the
   other portion for customer (subscriber) or other address pool use.
   Typically, the number of infrastructure addresses needed is
   relatively small in comparison to the total address count.  So unless
   the ISP was only granted a small public block, dedicating some



Kirkham                 Expires September 6, 2012               [Page 3]

Internet-Draft             private-ip-sp-cores                March 2012


   portion to infrastructure links and loopback addresses (/32) is
   rarely a large enough issue to outweigh the problems that are
   potentially caused when private address space is used.

   Additionally, specifications and equipment capability improvements
   now allow for the use of /31 subnets [RFC3021] for link addresses in
   place of the original /30 subnets - further minimising the impact of
   dedicating public addresses to infrastructure links by only using two
   (2) IP addresses per point to point link versus four (4)
   respectively.

   The use of private addressing as a conservation technique within an
   Internet Service Provider (ISP) core can cause a number of technical
   and operational issues or effects.  The main effects are described
   below.


3.  Effects on Traceroute

   The single biggest effect caused by the use of private (RFC1918)
   addressing within an Internet core is the fact that it can disrupt
   the operation of traceroute in some situations.  This section
   provides some examples of the issues that can occur.

   A first example illustrates the situation where the traceroute
   crosses an AS boundary and one of the networks has utilised private
   addressing.  The following simple network is used to show the
   effects.


              AS64496                 EBGP                AS64497
                    IBGP Mesh <--------------->  IBGP Mesh

R1 Pool -                                                      R6 Pool -
203.0.113.0/26                                          203.0.113.64/26

                               198.51.100.8/30
                                             198.51.100.4/30
    10.1.1.0/30  10.1.1.4/30                             198.51.100.0/30
                               .9          .10
    .1       .2  .5       .6    ------------    .6      .5  .2      .1
  R1-----------R2-----------R3--|          |--R4----------R5----------R6


  R1 Loopback: 10.1.1.101                    R4 Loopback: 198.51.100.103
  R2 Loopback: 10.1.1.102                    R5 Loopback: 198.51.100.102
  R3 Loopback: 10.1.1.103                    R6 Loopback: 198.51.100.101




Kirkham                 Expires September 6, 2012               [Page 4]

Internet-Draft             private-ip-sp-cores                March 2012


   Using this example, performing the traceroute from AS64497 to
   AS64496, we can see the private addresses of the infrastructure links
   in AS64496 are returned.

   R6#traceroute 203.0.113.1
   Type escape sequence to abort.
   Tracing the route to 203.0.113.1

     1 198.51.100.2 40 msec 20 msec 32 msec
     2 198.51.100.6 16 msec 20 msec 20 msec
     3 198.51.100.9 20 msec 20 msec 32 msec
     4 10.1.1.5 20 msec 20 msec 20 msec
     5 10.1.1.1 20 msec 20 msec 20 msec
   R6#


   This effect in itself is often not a problem.  However, if anti-
   spoofing controls are applied at network perimeters, then responses
   returned from hops with private IP addresses will be dropped.  Anti-
   spoofing refers to a security control where traffic with an invalid
   source address is discarded.  Anti-spoofing is further described in
   BCP 38/RFC 2827.

   The effects are illustrated in a second example below.  The same
   network as example 1 is used, but with the addition of anti-spoofing
   deployed at the ingress of R4 on the R3-R4 interface (ip address
   198.51.100.10).

   R6#traceroute 203.0.113.1

   Type escape sequence to abort.
   Tracing the route to 203.0.113.1

     1 198.51.100.2 24 msec 20 msec 20 msec
     2 198.51.100.6 20 msec 52 msec 44 msec
     3 198.51.100.9 44 msec 20 msec 32 msec
     4  *  *  *
     5  *  *  *
     6  *  *  *
     7  *  *  *
     8  *  *  *
     9  *  *  *
    10  *  *  *
    11  *  *  *
    12  *  *  *

   In a third example, a similar effect is caused.  If a traceroute is
   initiated from a router with a private (source) IP address, located



Kirkham                 Expires September 6, 2012               [Page 5]

Internet-Draft             private-ip-sp-cores                March 2012


   in AS64496 and the destination is outside of the ISPs AS (AS64497),
   then in this situation the traceroute will fail completely beyond the
   AS boundary.

   R1# traceroute 203.0.113.65
   Type escape sequence to abort.
   Tracing the route to 203.0.113.65

     1 10.1.1.2 20 msec 20 msec 20 msec
     2 10.1.1.6 52 msec 24 msec 40 msec
     3  *  *  *
     4  *  *  *
     5  *  *  *
     6  *  *  *
   R1#

   While it is completely unreasonable to expect a packet with a private
   source address to be successfully returned in a typical SP
   environment, the case is included to show the effect as it can have
   implications for troubleshooting.  This case will be referenced in a
   later section.

   In a complex topology, with multiple paths and exit points, the
   provider will lose their ability to trace paths originating within
   their own AS, through their network, to destinations within other
   ASs.  Such a situation could be a severe troubleshooting impediment.

   For completeness, a fourth example is included to show that a
   successful traceroute can be achieved by specifying a public source
   address as the source address of the traceroute.  Such an approach
   can be used in many operational situations if the router initiating
   the traceroute has at least one public address configured.  However,
   the approach is more cumbersome.


















Kirkham                 Expires September 6, 2012               [Page 6]

Internet-Draft             private-ip-sp-cores                March 2012


   R1#traceroute
   Protocol [ip]:
   Target IP address: 203.0.113.65
   Source address: 203.0.113.1
   Numeric display [n]:
   Timeout in seconds [3]:
   Probe count [3]:
   Minimum Time to Live [1]:
   Maximum Time to Live [30]: 10
   Port Number [33434]:
   Loose, Strict, Record, Timestamp, Verbose[none]:
   Type escape sequence to abort.
   Tracing the route to 203.0.113.65

     1 10.1.1.2 0 msec 4 msec 0 msec
     2 10.1.1.6 0 msec 4 msec 0 msec
     3 198.51.100.10 [AS 64497] 0 msec 4 msec 0 msec
     4 198.51.100.5 [AS 64497] 0 msec 0 msec 4 msec
     5 198.51.100.1 [AS 64497] 0 msec 0 msec 4 msec
   R1#

   It should be noted that some solutions to this problem have been
   proposed in RFC 5837 which provides extensions to ICMP to allow the
   identification of interfaces and their components by any combination
   of the following:  ifIndex, IPv4 address, IPv6 address, name, and
   MTU.  However at the time of writing, little or no deployment was
   known to be in place.


4.  Effects on Path MTU Discovery

   The Path MTU Discovery (PMTUD) process was designed to allow hosts to
   make an accurate assessment of the maximum packet size that can be
   sent across a path without fragmentation.  Path MTU Discovery is
   supported for TCP (and other protocols that support PMTUD such as GRE
   and IPsec) and works as follows:

   o When a router attempts to forward an IP datagram with the Do Not
   Fragment (DF) bit set out a link that has a lower MTU than the size
   of the packet, the router MUST drop the packet and return an Internet
   Control Message Protocol (ICMP) 'destination unreachable -
   fragmentation needed and DF set (type 3, code 4)' message to the
   source of the IP datagram.  This message includes the MTU of that
   next-hop network.  As a result, the source station which receives the
   ICMP message, will lower the send Maximum Segment Size (MSS).

   It is obviously desirable that packets be sent between two
   communicating hosts without fragmentation as this process imposes



Kirkham                 Expires September 6, 2012               [Page 7]

Internet-Draft             private-ip-sp-cores                March 2012


   extra load on the fragmenting router (process of fragmentation),
   intermediate routers (forwarding additional packets), as well as the
   receiving host (reassembly of the fragmented packets).  Additionally,
   many applications, including some web servers, set the DF (do not
   fragment) bit causing undesirable interactions if the path MTU is
   insufficient.  Other TCP implementations may set an MTU size of 576
   bytes if PMTUD is unavailable.  In addition, IPsec and other
   tunneling protocols will often require MTUs greater than 1500 bytes
   and often rely on PMTUD.

   While it is uncommon these days for core SP networks not to support
   path MTUs in excess of 1500 bytes (with 4470 or greater being
   common), the situation of 1500 byte path MTUs is still common in many
   ethernet edge or aggregation networks.

   The issue is as follows:

   o When an ICMP Type 3 Code 4 message is issued from an infrastructure
   link that uses a private (RFC1918) address, it must be routed back to
   the originating host.  As the originating host will typically be a
   globally routable IP address, its source address is used as the
   destination address of the returned ICMP Type 3 packet.  At this
   point there are normally no problems.

   o As the returned packet will have an RFC1918 source address,
   problems can occur when the returned packet passes through an anti-
   spoofing security control (such as Unicast RPF (uRPF)), other anti-
   spoofing ACLs, or virtually any perimeter firewall.  These devices
   will typically drop packets with an RFC1918 source address, breaking
   the successful operation of PMTUD.

   As a result, the potential for application level issues may be
   created.


5.  Unexpected interactions with some NAT implementations

   Private addressing is legitimately used within many enterprise,
   corporate or government networks for internal network addressing.
   When users on the inside of the network require Internet access, they
   will typically connect through a perimeter router, firewall, or
   network proxy, that provides Network Address Translation (NAT) or
   Network Address Port Translation (NAPT) services to a public
   interface.

   Scarcity of public IPv4 addresses, and the transition to IPv6, is
   forcing many service providers to make use of NAT.  CGN (Carrier
   Grade NAT) will enable service providers to assign private RFC 1918



Kirkham                 Expires September 6, 2012               [Page 8]

Internet-Draft             private-ip-sp-cores                March 2012


   IPv4 addresses to their customers rather than public, globally unique
   IPv4 addresses.  NAT444 will make use of a double NAT process.

   Unpredictable or confusing interactions could occur if traffic such
   as traceroute, PMTUD and possibly other applications were launched
   from the NAT IPv4 'inside address' and it passed over the same
   address range in the public IP core.  While such a situation would be
   unlikely to occur if the NAT pools and the private infrastructure
   addressing were under the same administration, such a situation could
   occur in the more typical situation of a NAT'ed corporate network
   connecting to an ISP.  For example, say if 10.1.1.0/24 is used to
   internally number the corporate network.  A traceroute or PMTUD
   request is initiated inside the corporate network from say 10.1.1.1.
   The packet passes through a NAT (or NAPT) gateway, then over an ISP
   core numbered from the same range.  When the responses are delivered
   back to the originator, the returned packets from the privately
   addressed part of the ISP core could have an identical source and
   destination address of 10.1.1.1.



            NAT Pool -
           203.0.113.0/24

    10.1.1.0/30                 10.1.1.0/30              198.51.100.0/30
               198.51.100.12/30                198.51.100.4/30

    .1       .2  .14     .13  .1           .2  .6      .5  .2      .1
  R1-----------R2-----------R3---------------R4----------R5----------R6
               NAT
                                                          R6 Loopback:
                                                          198.51.100.100


   R1#traceroute 198.51.100.100

   Type escape sequence to abort.
   Tracing the route to 198.51.100.100

     1 10.1.1.2 0 msec 0 msec 0 msec
     2 198.51.100.13 0 msec 4 msec 0 msec
     3 10.1.1.2 0 msec 4 msec 0 msec        <<<<
     4 198.51.100.5 4 msec 0 msec 4 msec
     5 198.51.100.1 0 msec 0 msec 0 msec
   R1#

   This example has been included to illustrate an effect.  Whether that
   effect would be problematic would depend on both the deployment



Kirkham                 Expires September 6, 2012               [Page 9]

Internet-Draft             private-ip-sp-cores                March 2012


   scenario and the application in use.

   Certainly a scenario where the same RFC1918 address space becomes
   utilised on both the inside and outside interfaces of a NAT/NAPT
   device can be problematic.  For example, the same private address
   range is assigned by both the administrator of a corporate network
   and their ISP.  Some applications discover the outside address of
   their local CPE to determine if that address is reserver for special
   use.  Application behavior may then be based on this determination.
   [weil-shared-transition-space-request] provides further analysis of
   this situation.

   To address this scenario and others, at the time of writing, work was
   in progress to obtain a dedicated /10 address block for the purpose
   of Shared CGN (Carrier Grade NAT) Address Space.  Please refer to
   [bdgks-arin-shared-transition-space] and [weil-shared-transition-
   space-request] for details.  The purpose of Shared CGN Address Space
   is to number CPE (Customer Premise Equipment) interfaces that connect
   to CGN devices.  As explained in [weil-shared-transition-space-
   request], RFC1918 addressing has issues when used in this deployment
   scenario.


6.  Interactions with edge anti-spoofing techniques

   Denial of service attacks and distributed denial of attacks can make
   use of spoofed source IP addresses in an attempt to obfuscate the
   source of an attack.  RFC2827 (Network Ingress Filtering) strongly
   recommends that providers of Internet connectivity implement
   filtering to prevent packets using source addresses outside of their
   legitimately assigned and advertised prefix ranges.  Such filtering
   should also prevent packets with private source addresses from
   egressing the AS.

   Best security practices for ISPs also strongly recommend that packets
   with illegitimate source addresses should be dropped at the AS
   perimeter.  Illegitimate source addresses includes private IP
   (RFC1918) addresses, addresses within the provider's assigned prefix
   ranges, and bogons (legitimate but unassigned IP addresses).
   Additionally, packets with private IP destination addresses should
   also be dropped at the AS perimeter.

   If such filtering is properly deployed, then traffic either sourced
   from, or destined for privately addressed portions of the network
   should be dropped.  Hence the negative consequences on traceroute,
   PMTUD and regular ping type traffic.





Kirkham                 Expires September 6, 2012              [Page 10]

Internet-Draft             private-ip-sp-cores                March 2012


7.  Peering using loopbacks

   Although not a common technique, some ISPs use the loopback addresses
   of border routers (ASBRs) for peering, in particular where multiple
   connections or exchange points exist between the two ISPs.  Such a
   technique is used by some ISPs as the foundation of fine grained
   traffic engineering and load balancing through the combination of IGP
   metrics and multi-hop BGP.  When private or non-globally reachable
   addresses are used as loopback addresses, this technique is either
   not possible, or considerably more complex to implement.


8.  DNS Interaction

   Many ISPs utilise their DNS to perform both forward and reverse
   resolution for the infrastructure devices and infrastructure
   addresses.  With a privately numbered core, the ISP itself will still
   have the capability to perform name resolution of their own
   infrastructure.  However others outside of the autonomous system will
   not have this capability.  At best, they will get a number of
   unidentified RFC1918 IP addresses returned from a traceroute.

   It is also worth noting that in some cases the reverse resolution
   requests may leak outside of the AS.  Such a situation can add load
   to public DNS servers.  Further information on this problem is
   documented in the internet draft "AS112 Nameserver Operations".


9.  Operational and Troubleshooting issues

   Previous sections of the document have noted issues relating to
   network operations and troubleshooting.  In particular when private
   IP addressing within an ISP core is used, the ability to easily
   troubleshoot across the AS boundary may be limited.  In some cases
   this may be a serious troubleshooting impediment.  In other cases, it
   may be solved through the use of alternative troubleshooting
   techniques.

   The key point is that the flexibility of initiating an outbound ping
   or traceroute from a privately numbered section of the network is
   lost.  In a complex topology, with multiple paths and exit points
   from the AS, the provider may be restricted in their ability to trace
   paths through the network to other ASs.  Such a situation could be a
   severe troubleshooting impediment.

   For users outside of the AS, the loss of the ability to use a
   traceroute for troubleshooting is very often a serious issue.  As
   soon as many of these people see a row of "* * *" in a traceroute



Kirkham                 Expires September 6, 2012              [Page 11]

Internet-Draft             private-ip-sp-cores                March 2012


   they often incorrectly assume that a large part of the network is
   down or inaccessible (e.g. behind a firewall).  Operational
   experience in many large providers has shown that significant
   confusion can result.


10.  Security Considerations

   One of the arguments often put forward for the use of private
   addressing within an ISP is an improvement in the network security.
   It has been argued that if private addressing is used within the
   core, the network infrastructure becomes unreachable from outside the
   providers autonomous system, hence protecting the infrastructure.
   There is legitimacy to this argument.  Certainly if the core is
   privately numbered and unreachable, it potentially provides a level
   of isolation in addition to what can be achieved with other
   techniques, such as infrastructure ACLs, on their own.  This is
   especially true in the event of an ACL misconfiguration, something
   that does commonly occur as the result of human error.

   There are three key security gaps that exist in a privately addressed
   IP core.

      The approach does not protect against reflection attacks if edge
      anti-spoofing is not deployed.  For example, if a packet with
      spoofed source address corresponding to the networks
      infrastructure address range, is sent to a host (or other device)
      attached to the network, that host will send its response directly
      to the infrastructure address.  If such an attack was performed
      across a large number of hosts, then a successful large scale
      denial of service attack on the infrastructure could be achieved.
      This is not to say that a publicly numbered core will protect from
      the same attack, it won't.  The key point is that a reflection
      attack does get around the apparent security offered in a
      privately addressed core.

      Even if anti-spoofing is deployed at the AS boundary, the border
      routers will potentially carry routing information for the
      privately addressed network infrastructure.  This can mean that
      packets with spoofed addresses, corresponding to the private
      infrastructure addressing, may be considered legitimate by edge
      anti-spoofing techniques such as Unicast Reverse Path Forwarding -
      Loose Mode, and forwarded.  To avoid this situation, an edge anti-
      spoofing algorithm such as Unicast Reverse Path Forwarding -
      Strict Mode, would be required.  Strict approaches can be
      problematic in some environments or where asymmetric traffic paths
      exist.




Kirkham                 Expires September 6, 2012              [Page 12]

Internet-Draft             private-ip-sp-cores                March 2012


      The approach on its own does not protect the network
      infrastructure from directly connected customers (i.e. within the
      same AS).  Unless other security controls, such as access control
      lists (ACLs), are deployed at the ingress point of the network,
      customer devices will normally be able to reach, and potentially
      attack, both core and edge infrastructure devices.


11.  Alternate approaches to core network security

   Today, hardware-based ACLs, which have minimal to no performance
   impact, are now widespread.  Applying an ACL at the AS perimeter to
   prevent access to the network core may be a far simpler approach and
   provide comparable protection to using private addressing, Such a
   technique is known as an infrastructure ACL (iACL).

   In concept, iACLs provide filtering at the edge network which allows
   traffic to cross the network core, but not to terminate on
   infrastructure addresses within the core.  Proper iACL deployment
   will normally allow required network management traffic to be passed,
   such that traceroutes and PMTUD can still operate successfully.  For
   an iACL deployment to be practical, the core network needs to have
   been addressed with a relatively small number of contiguous address
   blocks.  For this reason, the technique may or may not be practical.

   A second approach to preventing external access to the core is IS-IS
   core hiding.  This technique makes use of a fundamental property of
   the IS-IS protocol which allows link addresses to be removed from the
   routing table while still allowing loopback addresses to be resolved
   as next hops for BGP.  The technique prevents parties outside the AS
   from being able to route to infrastructure addresses, while still
   allowing traceroutes to operate successfully.  IS-IS core hiding does
   not have the same practical requirement for the core to be addressed
   from a small number of contiguous address blocks as with iACLs.  From
   an operational and troubleshooting perspective, care must be taken to
   ensure that pings and traceroutes are using source and destination
   addresses that exist in the routing tables of all routers in the
   path. i.e.  Not hidden link addresses.

   A third approach is the use of either an MPLS based IP VPN, or an
   MPLS based IP Core where the 'P' routers (or Label Switch Routers) do
   not carry global routing information.  As the core 'P' routers (or
   Label Switch Routers) are only switching labeled traffic, they are
   effectively not reachable from outside of the MPLS domain.  The 'P'
   routers can optionally be hidden such they do not appear in a
   traceroute.  While this approach isolates the 'P' routers from
   directed attacks, it does not protect the edge routers - being either
   a 'PE' router or a Label Edge Router (LER).  Obviously there are



Kirkham                 Expires September 6, 2012              [Page 13]

Internet-Draft             private-ip-sp-cores                March 2012


   numerous other engineering considerations in such an approach, we
   simply note it as an option.

   These techniques may not be suitable for every network, however,
   there are many circumstances where they can be used successfully
   without the associated effects of a privately addressing the core.


12.  Normative References

   [RFC1191]  Mogul, J. and S. Deering, "Path MTU Discovery",
              November 1990.

   [RFC1393]  Malkin, G., "Traceroute Using an IP Option", January 1993.

   [RFC1918]  Rekhter , Y., Moskowitz, R., Karrenberg, D., Jan de Groot,
              G., and E. Lear , "RFC1918 Address Allocation for Private
              Internets, BCP 5", Febuary  1996.

   [RFC2728]  Ferguson, P. and D. Senie , "RFC 2827 Network Ingress
              Filtering, BCP 38", May 2000.

   [RFC3021]  Retana, A., White, R., Fuller, V., and D. McPherson,
              "Using 31-Bit Prefixes on IPv4 Point-to-Point Links",
              December 2000.

   [RFC6304]  Abley, J. and W. Maton, "AS112 Nameserver Operations",
              July 2011.

   [RFC792]   Postel, J., "RFC792 Internet Control Message Protocol",
              September 1981.

   [bdgks-arin-shared-transition-space]
              Barber, S., Delong, O., Grundemann, C., Kuarsingh, V., and
              B. Schliesser, "ARIN Draft Policy 2011-5: Shared
              Transition Space".

   [weil-shared-transition-space-request]
              Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and
              M. Azinger, "IANA Reserved IPv4 Prefix for Shared CGN
              Space".


Appendix A.  Acknowledgments

   The author would like to thank the following people for their input
   and review - Dan Wing (Cisco Systems), Roland Dobbins (Arbor
   Networks), Philip Smith (APNIC), Barry Greene (ISC), Anton Ivanov



Kirkham                 Expires September 6, 2012              [Page 14]

Internet-Draft             private-ip-sp-cores                March 2012


   (kot-begemot.co.uk), Ryan Mcdowell (Cisco Systems), Russ White (Cisco
   Systems), Gregg Schudel (Cisco Systems), Michael Behringer (Cisco
   Systems), Stephan Millet (Cisco Systems), Tom Petch (BT Connect), Wes
   George (Time Warner Cable).

   The author would also like to acknowledge the use of a variety of
   NANOG mail archives as references.


Index

   H
      http://tools.ietf.org/html/draft-ietf-dnsop-as112-ops-08  11
      http://tools.ietf.org/html/rfc2827  5


Author's Address

   Anthony Kirkham
   Palo Alto Networks
   Level 32, 100 Miller St
   North Sydney, New South Wales  2060
   Australia

   Phone:  +61 7 33530902
   Email:  tkirkham@paloaltonetworks.com

























Kirkham                 Expires September 6, 2012              [Page 15]


--------------010106000702080907090302
Content-Type: text/xml;
 name="draft-ietf-grow-private-ip-sp-cores-00.xml"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment;
 filename="draft-ietf-grow-private-ip-sp-cores-00.xml"

<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type='text/xsl' href='rfc2629-fixed.xslt' ?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY ADDARCH SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3513.xml">
<!ENTITY GLOBAL SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3587.xml">
<!ENTITY ICMPv6 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4443.xml">
<!ENTITY IPv6 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2460.xml">
<!ENTITY NTP SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1305.xml">
<!ENTITY RANDOM SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4086.xml">
<!ENTITY SHA1 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3174.xml">
<!ENTITY ULA SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4193.xml">
<!ENTITY FIPS SYSTEM "http://xml.resource.org/public/rfc/bibxml2/reference.FIPS.180-1.1995.xml">
]>
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="no"?>
<?rfc inline="yes"?>
<?rfc subcompact="no"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes"?>
<?rfc compact="yes" ?>
<?rfc sortrefs="yes" ?>
<?rfc colonspace='yes' ?>
<rfc category="info" docName="draft-ietf-grow-private-ip-sp-cores-00"
     ipr="trust200902" obsoletes="None" submissionType="IETF" updates=""
     xml:lang="en">
  <front>
    <title abbrev="private-ip-sp-cores">Issues with Private IP Addressing in
    the Internet</title>

    <author fullname="Anthony Kirkham" initials="A." surname="Kirkham">
      <organization>Palo Alto Networks</organization>

      <address>
        <postal>
          <street>Level 32, 100 Miller St</street>

          <street></street>

          <city>North Sydney</city>

          <region>New South Wales</region>

          <code>2060</code>

          <country>Australia</country>
        </postal>

        <phone>+61 7 33530902</phone>

        <email>tkirkham@paloaltonetworks.com</email>
      </address>
    </author>

    <date day="5" month="March" year="2012" />

    <abstract>
      <t>The purpose of this document is to provide a discussion of the
      potential problems of using private, RFC1918, or non-globally-routable
      addressing within the core of an SP network. The discussion focuses on
      link addresses and to a small extent loopback addresses. While many of
      the issues are well recognised within the ISP community, there appears
      to be no document that collectively describes the issues.</t>
    </abstract>

    <note title="Legal">
      <t>This documents and the information contained therein are provided on
      an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
      OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
      THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
      IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
      INFORMATION THEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
      WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.</t>
    </note>
  </front>

  <middle>
    <section title="Introduction" toc="default">
      <t>In the mid to late 90's, some Internet Service Providers (ISPs)
      adopted the practice of utilising private (or non-globally unique) IP
      (i.e. RFC1918) addresses for the infrastructure links and in some cases
      the loopback interfaces within their networks. The reasons for this
      approach centered on conservation of address space (i.e. scarcity of
      public IPv4 address space), and security of the core network (also known
      as core hiding).</t>

      <t>However, a number of technical and operational issues occurred as a
      result of using private (or non-globally unique) IP addresses, and
      virtually all these ISPs moved away from the practice. Tier 1 ISPs are
      considered the benchmark of the industry and as of the time of writing,
      there is no known tier 1 ISP that utilises the practice of private
      addressing within their core network.</t>

      <t>The following sections will discuss the various issues associated
      with deploying private IP (i.e. RFC1918) addresses within ISP core
      networks.</t>

      <t>The intent of this document is not to suggest that private IP can not
      be used with the core of an SP network as some providers use this
      practice and operate successfully. The intent is to outline the
      potential issues or effects of such a practice.</t>

      <t>Note: The practice of ISPs using ‘stolen’ address space (also known
      as 'squat' space) has many of the same issues (or effects) as that of
      using private IP address space within core networks. The term “stolen IP
      address space” refers to the practice of an ISP using address space for
      its own infrastructure/core network addressing that has been officially
      allocated by an RIR to another provider, but that provider is not
      currently using or advertising within the Internet. Stolen addressing is
      not discussed further in this document. It is simply noted as an
      associated issue.</t>
    </section>

    <section title="Conservation of Address Space">
      <t>One of the original intents for the use of private IP addressing
      within an ISP core was the conservation of IP address space. When an ISP
      is allocated a block of public IP addresses (from a RIR), this address
      block was traditionally split in order to dedicate some portion for
      infrastructure use (i.e. for the core network), and the other portion
      for customer (subscriber) or other address pool use. Typically, the
      number of infrastructure addresses needed is relatively small in
      comparison to the total address count. So unless the ISP was only
      granted a small public block, dedicating some portion to infrastructure
      links and loopback addresses (/32) is rarely a large enough issue to
      outweigh the problems that are potentially caused when private address
      space is used.</t>

      <t>Additionally, specifications and equipment capability improvements
      now allow for the use of /31 subnets [RFC3021] for link addresses in
      place of the original /30 subnets – further minimising the impact of
      dedicating public addresses to infrastructure links by only using two
      (2) IP addresses per point to point link versus four (4)
      respectively.</t>

      <t>The use of private addressing as a conservation technique within an
      Internet Service Provider (ISP) core can cause a number of technical and
      operational issues or effects. The main effects are described below.</t>
    </section>

    <section title="Effects on Traceroute">
      <t>The single biggest effect caused by the use of private (RFC1918)
      addressing within an Internet core is the fact that it can disrupt the
      operation of traceroute in some situations. This section provides some
      examples of the issues that can occur.</t>

      <t>A first example illustrates the situation where the traceroute
      crosses an AS boundary and one of the networks has utilised private
      addressing. The following simple network is used to show the
      effects.</t>

      <figure>
        <artwork>

              AS64496                 EBGP                AS64497
                    IBGP Mesh &lt;---------------&gt;  IBGP Mesh

R1 Pool -                                                      R6 Pool -
203.0.113.0/26                                          203.0.113.64/26

                               198.51.100.8/30 
                                             198.51.100.4/30
    10.1.1.0/30  10.1.1.4/30                             198.51.100.0/30
                               .9          .10   
    .1       .2  .5       .6    ------------    .6      .5  .2      .1
  R1-----------R2-----------R3--|          |--R4----------R5----------R6


  R1 Loopback: 10.1.1.101                    R4 Loopback: 198.51.100.103
  R2 Loopback: 10.1.1.102                    R5 Loopback: 198.51.100.102
  R3 Loopback: 10.1.1.103                    R6 Loopback: 198.51.100.101
</artwork>
      </figure>

      <t>Using this example, performing the traceroute from AS64497 to
      AS64496, we can see the private addresses of the infrastructure links in
      AS64496 are returned.</t>

      <figure>
        <artwork>
R6#traceroute 203.0.113.1
Type escape sequence to abort.
Tracing the route to 203.0.113.1

  1 198.51.100.2 40 msec 20 msec 32 msec
  2 198.51.100.6 16 msec 20 msec 20 msec
  3 198.51.100.9 20 msec 20 msec 32 msec
  4 10.1.1.5 20 msec 20 msec 20 msec
  5 10.1.1.1 20 msec 20 msec 20 msec 
R6#

</artwork>
      </figure>

      <t>This effect in itself is often not a problem. However, if
      anti-spoofing controls are applied at network perimeters, then responses
      returned from hops with private IP addresses will be dropped.
      Anti-spoofing refers to a security control where traffic with an invalid
      source address is discarded. Anti-spoofing is further described in BCP
      38/RFC 2827.</t>

      <iref item="http://tools.ietf.org/html/rfc2827" primary="true" />

      <t>The effects are illustrated in a second example below. The same
      network as example 1 is used, but with the addition of anti-spoofing
      deployed at the ingress of R4 on the R3-R4 interface (ip address
      198.51.100.10).</t>

      <figure>
        <artwork>
R6#traceroute 203.0.113.1

Type escape sequence to abort.
Tracing the route to 203.0.113.1

  1 198.51.100.2 24 msec 20 msec 20 msec
  2 198.51.100.6 20 msec 52 msec 44 msec
  3 198.51.100.9 44 msec 20 msec 32 msec
  4  *  *  * 
  5  *  *  * 
  6  *  *  * 
  7  *  *  * 
  8  *  *  * 
  9  *  *  * 
 10  *  *  * 
 11  *  *  * 
 12  *  *  * 
</artwork>
      </figure>

      <t>In a third example, a similar effect is caused. If a traceroute is
      initiated from a router with a private (source) IP address, located in
      AS64496 and the destination is outside of the ISPs AS (AS64497), then in
      this situation the traceroute will fail completely beyond the AS
      boundary.</t>

      <figure>
        <artwork>
R1# traceroute 203.0.113.65
Type escape sequence to abort.
Tracing the route to 203.0.113.65

  1 10.1.1.2 20 msec 20 msec 20 msec
  2 10.1.1.6 52 msec 24 msec 40 msec
  3  *  *  * 
  4  *  *  * 
  5  *  *  * 
  6  *  *  *
R1#  
</artwork>
      </figure>

      <t>While it is completely unreasonable to expect a packet with a private
      source address to be successfully returned in a typical SP environment,
      the case is included to show the effect as it can have implications for
      troubleshooting. This case will be referenced in a later section.</t>

      <t>In a complex topology, with multiple paths and exit points, the
      provider will lose their ability to trace paths originating within their
      own AS, through their network, to destinations within other ASs. Such a
      situation could be a severe troubleshooting impediment.</t>

      <t>For completeness, a fourth example is included to show that a
      successful traceroute can be achieved by specifying a public source
      address as the source address of the traceroute. Such an approach can be
      used in many operational situations if the router initiating the
      traceroute has at least one public address configured. However, the
      approach is more cumbersome.</t>

      <figure>
        <artwork>
R1#traceroute
Protocol [ip]: 
Target IP address: 203.0.113.65
Source address: 203.0.113.1
Numeric display [n]: 
Timeout in seconds [3]: 
Probe count [3]: 
Minimum Time to Live [1]: 
Maximum Time to Live [30]: 10
Port Number [33434]: 
Loose, Strict, Record, Timestamp, Verbose[none]: 
Type escape sequence to abort.
Tracing the route to 203.0.113.65

  1 10.1.1.2 0 msec 4 msec 0 msec
  2 10.1.1.6 0 msec 4 msec 0 msec
  3 198.51.100.10 [AS 64497] 0 msec 4 msec 0 msec
  4 198.51.100.5 [AS 64497] 0 msec 0 msec 4 msec
  5 198.51.100.1 [AS 64497] 0 msec 0 msec 4 msec 
R1#
</artwork>
      </figure>

      <t>It should be noted that some solutions to this problem have been
      proposed in RFC 5837 which provides extensions to ICMP to allow the
      identification of interfaces and their components by any combination of
      the following: ifIndex, IPv4 address, IPv6 address, name, and MTU.
      However at the time of writing, little or no deployment was known to be
      in place.</t>
    </section>

    <section title="Effects on Path MTU Discovery">
      <t>The Path MTU Discovery (PMTUD) process was designed to allow hosts to
      make an accurate assessment of the maximum packet size that can be sent
      across a path without fragmentation. Path MTU Discovery is supported for
      TCP (and other protocols that support PMTUD such as GRE and IPsec) and
      works as follows:</t>

      <t>• When a router attempts to forward an IP datagram with the Do Not
      Fragment (DF) bit set out a link that has a lower MTU than the size of
      the packet, the router MUST drop the packet and return an Internet
      Control Message Protocol (ICMP) 'destination unreachable - fragmentation
      needed and DF set (type 3, code 4)’ message to the source of the IP
      datagram. This message includes the MTU of that next-hop network. As a
      result, the source station which receives the ICMP message, will lower
      the send Maximum Segment Size (MSS).</t>

      <t>It is obviously desirable that packets be sent between two
      communicating hosts without fragmentation as this process imposes extra
      load on the fragmenting router (process of fragmentation), intermediate
      routers (forwarding additional packets), as well as the receiving host
      (reassembly of the fragmented packets). Additionally, many applications,
      including some web servers, set the DF (do not fragment) bit causing
      undesirable interactions if the path MTU is insufficient. Other TCP
      implementations may set an MTU size of 576 bytes if PMTUD is
      unavailable. In addition, IPsec and other tunneling protocols will often
      require MTUs greater than 1500 bytes and often rely on PMTUD.</t>

      <t>While it is uncommon these days for core SP networks not to support
      path MTUs in excess of 1500 bytes (with 4470 or greater being common),
      the situation of 1500 byte path MTUs is still common in many ethernet
      edge or aggregation networks.</t>

      <t>The issue is as follows:</t>

      <t>• When an ICMP Type 3 Code 4 message is issued from an infrastructure
      link that uses a private (RFC1918) address, it must be routed back to
      the originating host. As the originating host will typically be a
      globally routable IP address, its source address is used as the
      destination address of the returned ICMP Type 3 packet. At this point
      there are normally no problems.</t>

      <t>• As the returned packet will have an RFC1918 source address,
      problems can occur when the returned packet passes through an
      anti-spoofing security control (such as Unicast RPF (uRPF)), other
      anti-spoofing ACLs, or virtually any perimeter firewall. These devices
      will typically drop packets with an RFC1918 source address, breaking the
      successful operation of PMTUD.</t>

      <t>As a result, the potential for application level issues may be
      created.</t>
    </section>

    <section title="Unexpected interactions with some NAT implementations">
      <t>Private addressing is legitimately used within many enterprise,
      corporate or government networks for internal network addressing. When
      users on the inside of the network require Internet access, they will
      typically connect through a perimeter router, firewall, or network
      proxy, that provides Network Address Translation (NAT) or Network
      Address Port Translation (NAPT) services to a public interface.</t>

      <t>Scarcity of public IPv4 addresses, and the transition to IPv6, is
      forcing many service providers to make use of NAT. CGN (Carrier Grade
      NAT) will enable service providers to assign private RFC 1918 IPv4
      addresses to their customers rather than public, globally unique IPv4
      addresses. NAT444 will make use of a double NAT process.</t>

      <t>Unpredictable or confusing interactions could occur if traffic such
      as traceroute, PMTUD and possibly other applications were launched from
      the NAT IPv4 ‘inside address’ and it passed over the same address range
      in the public IP core. While such a situation would be unlikely to occur
      if the NAT pools and the private infrastructure addressing were under
      the same administration, such a situation could occur in the more
      typical situation of a NAT'ed corporate network connecting to an ISP.
      For example, say if 10.1.1.0/24 is used to internally number the
      corporate network. A traceroute or PMTUD request is initiated inside the
      corporate network from say 10.1.1.1. The packet passes through a NAT (or
      NAPT) gateway, then over an ISP core numbered from the same range. When
      the responses are delivered back to the originator, the returned packets
      from the privately addressed part of the ISP core could have an
      identical source and destination address of 10.1.1.1.</t>

      <figure>
        <artwork>


            NAT Pool -                                           
           203.0.113.0/24   
                                        
    10.1.1.0/30                 10.1.1.0/30              198.51.100.0/30
               198.51.100.12/30                198.51.100.4/30

    .1       .2  .14     .13  .1           .2  .6      .5  .2      .1
  R1-----------R2-----------R3---------------R4----------R5----------R6
               NAT
                                                          R6 Loopback:  
                                                          198.51.100.100
</artwork>
      </figure>

      <figure>
        <artwork>
R1#traceroute 198.51.100.100

Type escape sequence to abort.
Tracing the route to 198.51.100.100

  1 10.1.1.2 0 msec 0 msec 0 msec
  2 198.51.100.13 0 msec 4 msec 0 msec
  3 10.1.1.2 0 msec 4 msec 0 msec        &lt;&lt;&lt;&lt;
  4 198.51.100.5 4 msec 0 msec 4 msec
  5 198.51.100.1 0 msec 0 msec 0 msec 
R1#  
</artwork>
      </figure>

      <t>This example has been included to illustrate an effect. Whether that
      effect would be problematic would depend on both the deployment scenario
      and the application in use.</t>

      <t>Certainly a scenario where the same RFC1918 address space becomes
      utilised on both the inside and outside interfaces of a NAT/NAPT device
      can be problematic. For example, the same private address range is
      assigned by both the administrator of a corporate network and their ISP.
      Some applications discover the outside address of their local CPE to
      determine if that address is reserver for special use. Application
      behavior may then be based on this determination.
      [weil-shared-transition-space-request] provides further analysis of this
      situation.</t>

      <t>To address this scenario and others, at the time of writing, work was
      in progress to obtain a dedicated /10 address block for the purpose of
      Shared CGN (Carrier Grade NAT) Address Space. Please refer to
      [bdgks-arin-shared-transition-space] and
      [weil-shared-transition-space-request] for details. The purpose of
      Shared CGN Address Space is to number CPE (Customer Premise Equipment)
      interfaces that connect to CGN devices. As explained in
      [weil-shared-transition-space-request], RFC1918 addressing has issues
      when used in this deployment scenario.</t>
    </section>

    <section title="Interactions with edge anti-spoofing techniques">
      <t>Denial of service attacks and distributed denial of attacks can make
      use of spoofed source IP addresses in an attempt to obfuscate the source
      of an attack. RFC2827 (Network Ingress Filtering) strongly recommends
      that providers of Internet connectivity implement filtering to prevent
      packets using source addresses outside of their legitimately assigned
      and advertised prefix ranges. Such filtering should also prevent packets
      with private source addresses from egressing the AS.</t>

      <t>Best security practices for ISPs also strongly recommend that packets
      with illegitimate source addresses should be dropped at the AS
      perimeter. Illegitimate source addresses includes private IP (RFC1918)
      addresses, addresses within the provider's assigned prefix ranges, and
      bogons (legitimate but unassigned IP addresses). Additionally, packets
      with private IP destination addresses should also be dropped at the AS
      perimeter.</t>

      <t>If such filtering is properly deployed, then traffic either sourced
      from, or destined for privately addressed portions of the network should
      be dropped. Hence the negative consequences on traceroute, PMTUD and
      regular ping type traffic.</t>
    </section>

    <section title="Peering using loopbacks">
      <t>Although not a common technique, some ISPs use the loopback addresses
      of border routers (ASBRs) for peering, in particular where multiple
      connections or exchange points exist between the two ISPs. Such a
      technique is used by some ISPs as the foundation of fine grained traffic
      engineering and load balancing through the combination of IGP metrics
      and multi-hop BGP. When private or non-globally reachable addresses are
      used as loopback addresses, this technique is either not possible, or
      considerably more complex to implement.</t>
    </section>

    <section title="DNS Interaction">
      <t>Many ISPs utilise their DNS to perform both forward and reverse
      resolution for the infrastructure devices and infrastructure addresses.
      With a privately numbered core, the ISP itself will still have the
      capability to perform name resolution of their own infrastructure.
      However others outside of the autonomous system will not have this
      capability. At best, they will get a number of unidentified RFC1918 IP
      addresses returned from a traceroute.</t>

      <t>It is also worth noting that in some cases the reverse resolution
      requests may leak outside of the AS. Such a situation can add load to
      public DNS servers. Further information on this problem is documented in
      the internet draft "AS112 Nameserver Operations".</t>

      <iref item="http://tools.ietf.org/html/draft-ietf-dnsop-as112-ops-08"
            primary="true" />
    </section>

    <section title="Operational and Troubleshooting issues">
      <t>Previous sections of the document have noted issues relating to
      network operations and troubleshooting. In particular when private IP
      addressing within an ISP core is used, the ability to easily
      troubleshoot across the AS boundary may be limited. In some cases this
      may be a serious troubleshooting impediment. In other cases, it may be
      solved through the use of alternative troubleshooting techniques.</t>

      <t>The key point is that the flexibility of initiating an outbound ping
      or traceroute from a privately numbered section of the network is lost.
      In a complex topology, with multiple paths and exit points from the AS,
      the provider may be restricted in their ability to trace paths through
      the network to other ASs. Such a situation could be a severe
      troubleshooting impediment.</t>

      <t>For users outside of the AS, the loss of the ability to use a
      traceroute for troubleshooting is very often a serious issue. As soon as
      many of these people see a row of "* * *" in a traceroute they often
      incorrectly assume that a large part of the network is down or
      inaccessible (e.g. behind a firewall). Operational experience in many
      large providers has shown that significant confusion can result.</t>
    </section>

    <section title="Security Considerations">
      <t>One of the arguments often put forward for the use of private
      addressing within an ISP is an improvement in the network security. It
      has been argued that if private addressing is used within the core, the
      network infrastructure becomes unreachable from outside the providers
      autonomous system, hence protecting the infrastructure. There is
      legitimacy to this argument. Certainly if the core is privately numbered
      and unreachable, it potentially provides a level of isolation in
      addition to what can be achieved with other techniques, such as
      infrastructure ACLs, on their own. This is especially true in the event
      of an ACL misconfiguration, something that does commonly occur as the
      result of human error.</t>

      <t>There are three key security gaps that exist in a privately addressed
      IP core.<list>
          <t>The approach does not protect against reflection attacks if edge
          anti-spoofing is not deployed. For example, if a packet with spoofed
          source address corresponding to the networks infrastructure address
          range, is sent to a host (or other device) attached to the network,
          that host will send its response directly to the infrastructure
          address. If such an attack was performed across a large number of
          hosts, then a successful large scale denial of service attack on the
          infrastructure could be achieved. This is not to say that a publicly
          numbered core will protect from the same attack, it won’t. The key
          point is that a reflection attack does get around the apparent
          security offered in a privately addressed core.</t>

          <t>Even if anti-spoofing is deployed at the AS boundary, the border
          routers will potentially carry routing information for the privately
          addressed network infrastructure. This can mean that packets with
          spoofed addresses, corresponding to the private infrastructure
          addressing, may be considered legitimate by edge anti-spoofing
          techniques such as Unicast Reverse Path Forwarding – Loose Mode, and
          forwarded. To avoid this situation, an edge anti-spoofing algorithm
          such as Unicast Reverse Path Forwarding – Strict Mode, would be
          required. Strict approaches can be problematic in some environments
          or where asymmetric traffic paths exist.</t>

          <t>The approach on its own does not protect the network
          infrastructure from directly connected customers (i.e. within the
          same AS). Unless other security controls, such as access control
          lists (ACLs), are deployed at the ingress point of the network,
          customer devices will normally be able to reach, and potentially
          attack, both core and edge infrastructure devices.</t>
        </list></t>
    </section>

    <section title="Alternate approaches to core network security">
      <t>Today, hardware-based ACLs, which have minimal to no performance
      impact, are now widespread. Applying an ACL at the AS perimeter to
      prevent access to the network core may be a far simpler approach and
      provide comparable protection to using private addressing, Such a
      technique is known as an infrastructure ACL (iACL).</t>

      <t>In concept, iACLs provide filtering at the edge network which allows
      traffic to cross the network core, but not to terminate on
      infrastructure addresses within the core. Proper iACL deployment will
      normally allow required network management traffic to be passed, such
      that traceroutes and PMTUD can still operate successfully. For an iACL
      deployment to be practical, the core network needs to have been
      addressed with a relatively small number of contiguous address blocks.
      For this reason, the technique may or may not be practical.</t>

      <t>A second approach to preventing external access to the core is IS-IS
      core hiding. This technique makes use of a fundamental property of the
      IS-IS protocol which allows link addresses to be removed from the
      routing table while still allowing loopback addresses to be resolved as
      next hops for BGP. The technique prevents parties outside the AS from
      being able to route to infrastructure addresses, while still allowing
      traceroutes to operate successfully. IS-IS core hiding does not have the
      same practical requirement for the core to be addressed from a small
      number of contiguous address blocks as with iACLs. From an operational
      and troubleshooting perspective, care must be taken to ensure that pings
      and traceroutes are using source and destination addresses that exist in
      the routing tables of all routers in the path. i.e. Not hidden link
      addresses.</t>

      <t>A third approach is the use of either an MPLS based IP VPN, or an
      MPLS based IP Core where the 'P' routers (or Label Switch Routers) do
      not carry global routing information. As the core 'P' routers (or Label
      Switch Routers) are only switching labeled traffic, they are effectively
      not reachable from outside of the MPLS domain. The 'P' routers can
      optionally be hidden such they do not appear in a traceroute. While this
      approach isolates the 'P' routers from directed attacks, it does not
      protect the edge routers - being either a 'PE' router or a Label Edge
      Router (LER). Obviously there are numerous other engineering
      considerations in such an approach, we simply note it as an option.</t>

      <t>These techniques may not be suitable for every network, however,
      there are many circumstances where they can be used successfully without
      the associated effects of a privately addressing the core.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <reference anchor="RFC792">
        <front>
          <title>RFC792 Internet Control Message Protocol</title>

          <author initials="J" surname="Postel">
            <organization>ISI</organization>
          </author>

          <date month="September" year="1981" />
        </front>
      </reference>

      <reference anchor="RFC1191">
        <front>
          <title>Path MTU Discovery</title>

          <author initials="J" surname="Mogul">
            <organization>DECWRL</organization>
          </author>

          <author initials="S" surname="Deering">
            <organization>Stanford University</organization>
          </author>

          <date month="November" year="1990" />
        </front>
      </reference>

      <reference anchor="RFC1393">
        <front>
          <title>Traceroute Using an IP Option</title>

          <author initials="G" surname="Malkin">
            <organization>Xylogics, Inc.</organization>
          </author>

          <date month="January" year="1993" />
        </front>
      </reference>

      <reference anchor="RFC1918">
        <front>
          <title>RFC1918 Address Allocation for Private Internets, BCP
          5</title>

          <author initials="Y" surname="Rekhter ">
            <organization>Cisco Systems</organization>
          </author>

          <author initials="R" surname="Moskowitz">
            <organization>Chrysler Corporation</organization>
          </author>

          <author initials="D" surname="Karrenberg">
            <organization>RIPE Network Coordination Centre</organization>
          </author>

          <author initials="G" surname="Jan de Groot">
            <organization>RIPE Network Coordination Centre</organization>
          </author>

          <author initials="E" surname="Lear ">
            <organization>Silicon Graphics, Inc.</organization>
          </author>

          <date month="Febuary " year="1996" />
        </front>
      </reference>

      <reference anchor="RFC2728">
        <front>
          <title>RFC 2827 Network Ingress Filtering, BCP 38</title>

          <author initials="P" surname="Ferguson">
            <organization>Cisco Systems, Inc.</organization>
          </author>

          <author initials="D" surname="Senie ">
            <organization>Amaranth Networks Inc.</organization>
          </author>

          <date month="May" year="2000" />
        </front>
      </reference>

      <reference anchor="RFC3021">
        <front>
          <title>Using 31-Bit Prefixes on IPv4 Point-to-Point Links</title>

          <author initials="A" surname="Retana">
            <organization>Cisco Systems</organization>
          </author>

          <author initials="R" surname="White">
            <organization>Cisco Systems</organization>
          </author>

          <author initials="V" surname="Fuller">
            <organization>GTE Internetworking</organization>
          </author>

          <author initials="D" surname="McPherson">
            <organization>Amber Networks</organization>
          </author>

          <date month="December" year="2000" />
        </front>
      </reference>

      <reference anchor="RFC6304">
        <front>
          <title>AS112 Nameserver Operations</title>

          <author initials="J" surname="Abley">
            <organization>ICANN</organization>
          </author>

          <author initials="W" surname="Maton">
            <organization>NRC-CNRC</organization>
          </author>

          <date day="29" month="July" year="2011" />
        </front>
      </reference>

      <reference anchor="weil-shared-transition-space-request">
        <front>
          <title>IANA Reserved IPv4 Prefix for Shared CGN Space</title>

          <author initials="J" surname="Weil">
            <organization>Time Warner Cable</organization>
          </author>

          <author initials="V" surname="Kuarsingh">
            <organization>Rogers Communications</organization>
          </author>

          <author initials="C" surname="Donley">
            <organization>CableLabs</organization>
          </author>

          <author initials="C" surname="Liljenstolpe">
            <organization>Telstra Corp</organization>
          </author>

          <author initials="M" surname="Azinger">
            <organization>Frontier Communications</organization>
          </author>

          <date />
        </front>
      </reference>

      <reference anchor="bdgks-arin-shared-transition-space">
        <front>
          <title>ARIN Draft Policy 2011-5: Shared Transition Space</title>

          <author initials="S" surname="Barber">
            <organization>Cox Communications</organization>
          </author>

          <author initials="O" surname="Delong">
            <organization>Hurricane Electric</organization>
          </author>

          <author initials="C" surname="Grundemann">
            <organization>CableLabs</organization>
          </author>

          <author initials="V" surname="Kuarsingh">
            <organization>Rogers Communications</organization>
          </author>

          <author initials="B" surname="Schliesser">
            <organization>Cisco Systems</organization>
          </author>

          <date />
        </front>
      </reference>
    </references>

    <section title="Acknowledgments">
      <t>The author would like to thank the following people for their input
      and review – Dan Wing (Cisco Systems), Roland Dobbins (Arbor Networks),
      Philip Smith (APNIC), Barry Greene (ISC), Anton Ivanov
      (kot-begemot.co.uk), Ryan Mcdowell (Cisco Systems), Russ White (Cisco
      Systems), Gregg Schudel (Cisco Systems), Michael Behringer (Cisco
      Systems), Stephan Millet (Cisco Systems), Tom Petch (BT Connect), Wes
      George (Time Warner Cable).</t>

      <t>The author would also like to acknowledge the use of a variety of
      NANOG mail archives as references.</t>
    </section>
  </back>
</rfc>

--------------010106000702080907090302--

From christopher.morrow@gmail.com  Wed Mar  7 20:43:31 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B367A21E803E for <grow@ietfa.amsl.com>; Wed,  7 Mar 2012 20:43:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.549
X-Spam-Level: 
X-Spam-Status: No, score=-103.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 f561EiOlcNWG for <grow@ietfa.amsl.com>; Wed,  7 Mar 2012 20:43:31 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 09D6321F856D for <grow@ietf.org>; Wed,  7 Mar 2012 20:43:30 -0800 (PST)
Received: by obbta4 with SMTP id ta4so164126obb.31 for <grow@ietf.org>; Wed, 07 Mar 2012 20:43:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PhfSgFioZ2ZAgTGzu3T10zc5Qg90jejDo0h6sP/b04k=; b=yPUx1MT670l4TtIAl1cWtG9rgsPWgXBUA4k7abb9bZWwpbegj7fGVQ2vJYa0jMQyAF Uun3v7S60ETEXsrn/Ew0ARAwWnWHokTqLku9jKr2k41cTdrXcNkUpoLOcUmAviilqLp5 niJt7MiLVyplsCSYXNzCxuXEM/UcFVIyECWeXJxdwMKlz+4HbMnUiibK/CNJp8DAe1Ti euS3pIB+LZs6ZEpKmWyUkTeQR3EluZWBHL3rRHQge1/QSHi0cLpGVSO8Ndlvf4oRlA2f JoYnUJLNAXKznARZdwieDk2P3o0p0oEPxatCryO2WtDdI3pMbODetTEmaPhA73T4pX9I ZtCg==
MIME-Version: 1.0
Received: by 10.182.231.38 with SMTP id td6mr1783999obc.47.1331181810666; Wed, 07 Mar 2012 20:43:30 -0800 (PST)
Received: by 10.182.139.106 with HTTP; Wed, 7 Mar 2012 20:43:30 -0800 (PST)
In-Reply-To: <4F57D274.5000802@anthony-kirkham.com>
References: <4F57D274.5000802@anthony-kirkham.com>
Date: Wed, 7 Mar 2012 23:43:30 -0500
Message-ID: <CAL9jLaaSwJQRr6F7oCQPkyeLjPSGWyiiri8re5Sd93J+fKT4nQ@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: tkirkham@anthony-kirkham.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-private-ip-sp-cores-00
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 04:43:31 -0000

Let's all try to give this a read through, with an eye to start WGLC
Monday 3/11/2012, if there are no significant comments/complaints/etc
between now and then.

Thanks Anthony!
-chris

On Wed, Mar 7, 2012 at 4:26 PM, Anthony Kirkham
<tkirkham@anthony-kirkham.com> wrote:
> All,
>
> To cut a long story short, I had uploaded this draft through datatracker two
> moths back. For some reason it never seemed to have been posted. The
> material in this draft is essentially identical to the last individual
> submission I put forward. Since we are now in a blackout period, I will send
> (a re-dated version of 00) to the list. I believe this should be at last
> call status.
>
> Regards
> Tony K
>
> --
>
>
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>

From bruno.decraene@orange.com  Thu Mar  8 00:08:40 2012
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F35CA21F84DF for <grow@ietfa.amsl.com>; Thu,  8 Mar 2012 00:08:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=0.599,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
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 TYyWqvJaqfXQ for <grow@ietfa.amsl.com>; Thu,  8 Mar 2012 00:08:39 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 5CEF521F84DE for <grow@ietf.org>; Thu,  8 Mar 2012 00:08:37 -0800 (PST)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 27FD13B47AB; Thu,  8 Mar 2012 09:08:36 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 0DB1F35C0F5; Thu,  8 Mar 2012 09:08:36 +0100 (CET)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.01.0323.000; Thu, 8 Mar 2012 09:08:35 +0100
From: <bruno.decraene@orange.com>
To: Christopher Morrow <christopher.morrow@gmail.com>, "tkirkham@anthony-kirkham.com" <tkirkham@anthony-kirkham.com>
Thread-Topic: [GROW] draft-ietf-grow-private-ip-sp-cores-00
Thread-Index: AQHM/OYGq1xbC72pdEO/2zIV8m8tlpZgCYVw
Date: Thu, 8 Mar 2012 08:08:33 +0000
Message-ID: <29028_1331194116_4F586904_29028_1322_1_53C29892C857584299CBF5D05346208A02A10A@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <4F57D274.5000802@anthony-kirkham.com> <CAL9jLaaSwJQRr6F7oCQPkyeLjPSGWyiiri8re5Sd93J+fKT4nQ@mail.gmail.com>
In-Reply-To: <CAL9jLaaSwJQRr6F7oCQPkyeLjPSGWyiiri8re5Sd93J+fKT4nQ@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.3]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.1.19.234517
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] draft-ietf-grow-private-ip-sp-cores-00
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 08:08:40 -0000

I have not read the new -to be posted- version, but since the draft is said=
 to be essentially identical, I guess my previously comments still hold unc=
hanged.
http://www.ietf.org/mail-archive/web/grow/current/msg02119.html

Namely:

> - As the document targets the use of "non-globally- routable addressing
> within the core of an SP network", do you think you could extend the
> text to also include the use of public IP addresses (allocated to the
> SP) not advertised to the Internet (for security reason)?

> - For each problem considered (each section) could you summarize the
> conclusion for the 3 cases: private addresses, own public addresses not
> advertised, "stolen" public addresses not advertised. As depending on
> the section, theses 3 cases may not be equivalent.


Do you think the draft could be updated to address them? Possibly before a =
WGLC?

Thanks,
Regards,
Bruno

>From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of Ch=
ristopher Morrow
>Sent: Thursday, March 08, 2012 5:44 AM
>
>Let's all try to give this a read through, with an eye to start WGLC
>Monday 3/11/2012, if there are no significant comments/complaints/etc
>between now and then.
>
>Thanks Anthony!
>-chris
>
>On Wed, Mar 7, 2012 at 4:26 PM, Anthony Kirkham
><tkirkham@anthony-kirkham.com> wrote:
>> All,
>>
>> To cut a long story short, I had uploaded this draft through datatracker=
 two
>> moths back. For some reason it never seemed to have been posted. The
>> material in this draft is essentially identical to the last individual
>> submission I put forward. Since we are now in a blackout period, I will =
send
>> (a re-dated version of 00) to the list. I believe this should be at last
>> call status.
>>
>> Regards
>> Tony K
>>
>> --
>>
>>
>>
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>
>_______________________________________________
>GROW mailing list
>GROW@ietf.org
>https://www.ietf.org/mailman/listinfo/grow

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From wesley.george@twcable.com  Thu Mar  8 11:34:00 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7D7C21F865F; Thu,  8 Mar 2012 11:34:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.73
X-Spam-Level: 
X-Spam-Status: No, score=-0.73 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,  J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
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 RHxnQszaw05c; Thu,  8 Mar 2012 11:34:00 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 1B3AA21F8675; Thu,  8 Mar 2012 11:33:59 -0800 (PST)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.73,552,1325480400"; d="scan'208";a="350828265"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 08 Mar 2012 14:33:38 -0500
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.26]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Thu, 8 Mar 2012 14:33:59 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Chuck Anderson <cra@WPI.EDU>, "v6ops@ietf.org" <v6ops@ietf.org>, Anthony Kirkham <tkirkham@anthony-kirkham.com>
Date: Thu, 8 Mar 2012 14:33:58 -0500
Thread-Topic: [v6ops] New Draft: Using Only Link-Local Address in Network Core
Thread-Index: Acz9U6RMQtPs5mv8S7uNO+xYhpWncgADegtw
Message-ID: <DCC302FAA9FE5F4BBA4DCAD465693779173B6FB668@PRVPEXVS03.corp.twcable.com>
References: <51865E1A72F61D48A247348DCCBA5CFB05B9154C@XMB-AMS-105.cisco.com> <20120308173038.GI84425@Space.Net> <20120308173712.GT22535@angus.ind.WPI.EDU>
In-Reply-To: <20120308173712.GT22535@angus.ind.WPI.EDU>
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
Cc: "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [v6ops] New Draft: Using Only Link-Local Address in Network	Core
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 19:34:01 -0000

The proposed comparison already pretty much exists within a draft written a=
nd being adopted in GROW.

http://tools.ietf.org/html/draft-kirkham-private-ip-sp-cores-02


I'm thinking that perhaps the authors of the two drafts need to get togethe=
r and either bolster the discussion around IPv6 and link-local in the curre=
nt Kirkham draft, or turn this new draft into a companion document to -kirk=
ham so that we end up with two non-overlapping drafts, one that covers IPv4=
 and one that covers IPv6 with a similar format.

Thanks,

Wes George

> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of
> Chuck Anderson
> Sent: Thursday, March 08, 2012 12:37 PM
> To: v6ops@ietf.org
> Subject: Re: [v6ops] New Draft: Using Only Link-Local Address in Network =
Core
>

http://wiki.tools.ietf.org/html/draft-behringer-lla-only-00

> On Thu, Mar 08, 2012 at 06:30:38PM +0100, Gert Doering wrote:
> > > > Abstract
> > > >
> > > >   This document proposes to use only IPv6 link-local addresses on
> > > >   infrastructure links between routers, wherever possible.  It
> > > >   discusses the advantages and disadvantages of this approach to ai=
de
> > > >   the decision process for a given network,
> >
> > I'm perfectly fine with that abstract.  I just want to be sure that
> > this practice isn't advocated as a BCP to do so (because next thing our
> > customers or some crazy auditors will tell us that we do it all wrong).
>
> Perhaps the draft could be reworked to be a comparison and overview of
> both techniques, LLA and global addressing, and their pros/cons
> without having a position/recommendation/BCP for either method.
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From jhaas@slice.pfrc.org  Sun Mar 11 13:37:16 2012
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1784321F8731 for <grow@ietfa.amsl.com>; Sun, 11 Mar 2012 13:37:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level: 
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 5OWL8+ORYuV9 for <grow@ietfa.amsl.com>; Sun, 11 Mar 2012 13:37:15 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id A59CB21F86C6 for <grow@ietf.org>; Sun, 11 Mar 2012 13:37:15 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 73E281703E1; Sun, 11 Mar 2012 16:37:15 -0400 (EDT)
Date: Sun, 11 Mar 2012 16:37:15 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Anthony Kirkham <tkirkham@cisco.com>
Message-ID: <20120311203715.GG30627@slice>
References: <4E35F7CA.9000606@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4E35F7CA.9000606@cisco.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: grow@ietf.org
Subject: Re: [GROW] How to progress - Private IP in SP Core
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Mar 2012 20:37:16 -0000

Tony,

Note, I'm not speaking for the chairs or the ADs. 

On Mon, Aug 01, 2011 at 10:48:10AM +1000, Anthony Kirkham wrote:
> I'd appreciate any advice on how I might progress this draft. I'm
> reasonably happy with it now, but unsure how to take it the next
> step. I'd greatly appreciate any guidance.

Two paths are:
- Keep it as an individual submission and find an AD to sponsor the
  appropriate IESG review, etc:
  http://www.ietf.org/iesg/statement/ad-sponsoring-docs.html
- Get the GROW chairs to do some of this work for you by requesting adoption
  of the draft as a GROW WG document.  Glancing at the *very stale* charter,
  it's in scope for the WG.  IMO, given the amount of comment the draft has
  received to date, perhaps it should even just go through WGLC.

-- Jeff

P.S. to the GROW chairs - it's probably time for a recharter.  And I thought
the BFD milestones were stale! :-)

From jhaas@slice.pfrc.org  Sun Mar 11 13:45:20 2012
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13B9621F8735 for <grow@ietfa.amsl.com>; Sun, 11 Mar 2012 13:45:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.169
X-Spam-Level: 
X-Spam-Status: No, score=-102.169 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 kpXaYXfgj4qs for <grow@ietfa.amsl.com>; Sun, 11 Mar 2012 13:45:19 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 9CA1E21F8731 for <grow@ietf.org>; Sun, 11 Mar 2012 13:45:19 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 6A1831703DE; Sun, 11 Mar 2012 16:45:19 -0400 (EDT)
Date: Sun, 11 Mar 2012 16:45:19 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Jeffrey Haas <jhaas@pfrc.org>
Message-ID: <20120311204519.GH30627@slice>
References: <4E35F7CA.9000606@cisco.com> <20120311203715.GG30627@slice>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120311203715.GG30627@slice>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: grow@ietf.org, Anthony Kirkham <tkirkham@cisco.com>
Subject: Re: [GROW] How to progress - Private IP in SP Core
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Mar 2012 20:45:20 -0000

Sigh.  I replied to an item in an mis-sorted grow mailbox without checking
the date.  It looks like this was supported for WG adoption, but I still
don't see a matching draft-grow?

-- Jeff

On Sun, Mar 11, 2012 at 04:37:15PM -0400, Jeffrey Haas wrote:
> Tony,
> 
> Note, I'm not speaking for the chairs or the ADs. 
> 
> On Mon, Aug 01, 2011 at 10:48:10AM +1000, Anthony Kirkham wrote:
> > I'd appreciate any advice on how I might progress this draft. I'm
> > reasonably happy with it now, but unsure how to take it the next
> > step. I'd greatly appreciate any guidance.
> 
> Two paths are:
> - Keep it as an individual submission and find an AD to sponsor the
>   appropriate IESG review, etc:
>   http://www.ietf.org/iesg/statement/ad-sponsoring-docs.html
> - Get the GROW chairs to do some of this work for you by requesting adoption
>   of the draft as a GROW WG document.  Glancing at the *very stale* charter,
>   it's in scope for the WG.  IMO, given the amount of comment the draft has
>   received to date, perhaps it should even just go through WGLC.
> 
> -- Jeff
> 
> P.S. to the GROW chairs - it's probably time for a recharter.  And I thought
> the BFD milestones were stale! :-)
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From joe.gersch@secure64.com  Wed Mar 14 09:14:04 2012
Return-Path: <joe.gersch@secure64.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4072D21F85CD for <grow@ietfa.amsl.com>; Wed, 14 Mar 2012 09:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
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 7i4q309eIdYI for <grow@ietfa.amsl.com>; Wed, 14 Mar 2012 09:14:02 -0700 (PDT)
Received: from zimbra.secure64.com (unknown [64.92.221.189]) by ietfa.amsl.com (Postfix) with ESMTP id C484021F85C2 for <grow@ietf.org>; Wed, 14 Mar 2012 09:14:02 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.secure64.com (Postfix) with ESMTP id 77F42B84E1; Wed, 14 Mar 2012 10:14:01 -0600 (MDT)
X-Virus-Scanned: amavisd-new at secure64.com
Received: from zimbra.secure64.com ([127.0.0.1]) by localhost (zimbra.secure64.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7oylgcCwJb0W; Wed, 14 Mar 2012 10:13:59 -0600 (MDT)
Received: from [10.138.15.6] (unknown [192.168.254.4]) by zimbra.secure64.com (Postfix) with ESMTPSA id 0B28EB8488; Wed, 14 Mar 2012 10:13:58 -0600 (MDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=secure64.com; s=2010; t=1331741639; bh=enCwDVZaHIR3hJio21YW+swd94BfZUdVO6W2BxvSMjk=; h=Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=JoL3Mp8x+iIW +RMeo2jNSUZCvd9aBEwzlbZKccrx7IXvVw7VPrPMgkyzmFTwRzfJSOmf5UZ0bV54m2N BtNoY2I/SpYgee/wNI9IcEt1wJ7AN8FIM94LPNb7rJwbBMlmErW04e9FzHRylrVRDqo STrhGX5uwZiPROzXr2FkUm52I=
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Joseph Gersch <joe.gersch@secure64.com>
In-Reply-To: <CB7BAEBE.2272B%terry.manderson@icann.org>
Date: Wed, 14 Mar 2012 10:13:59 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4A95AAF-391A-452D-AD59-28A5F9DA546F@secure64.com>
References: <CB7BAEBE.2272B%terry.manderson@icann.org>
To: grow@ietf.org
X-Mailer: Apple Mail (2.1257)
Subject: Re: [GROW] New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 16:14:04 -0000

This thread is raising two questions:
   1) should the discussion be in GROW or SIDR?
   2) hasn't this idea been discussed before

--- Regarding the location for the draft,  the group presented arguments =
on both sides.    We believe that GROW is the proper place to lead the =
discussion.  However we have been invited to give a summary presentation =
at SIDR to ensure that all interested parties are aware of this =
proposal.  However, SIDR limits their scope to:   =20

> * Is an Autonomous System (AS) authorized to originate an IP prefix=20
> * Is the AS-Path represented in the route the same as the path through=20=

> which the NLRI traveled=20

Neither of these really fit our draft well.   You cannot use our =
approach to see all the prefixes that are authorized to originate from a =
given AS.   Instead of looking at prefix ranges or an AS,  this approach =
starts from a specific prefix and asks to identify its origin AS.   This =
is similar,  but not identical to what SIDR seeks to do.=20

The second SIDR objective does not fit our work at all.    We do not =
seek to validate a complete many hop path.    In this sense, we don't =
fit SIDR.    As we mentioned above,  we are interested in getting =
comments from SIDR,  but we feel GROW is a better fit.    In addition,  =
we have an operational testbed and are working to get more participants =
in operations.   This is something people can participate in now.   So =
in this sense,  we were shooting for something we view as more of a =
routing operation issue and hence GROW. =20

This proposal also impacts the DNSOP and DNSEXT groups.  We have asked =
people on those mailing lists for comments, and a presentation will be =
made at DNSOP as well.

--- Regarding the "already discussed issue":
   This earlier proposal was the T Bates / R Bush draft from 1998.  A =
lot of progress has taken place during the last 14 years.  The root zone =
and in-addr.arpa are signed with DNSSEC.   A naming convention for CIDR =
addresses in the reverse DNS is being proposed at DNSOP.   These new =
record types enable some interesting capabilities that are
worth discussing at GROW. =20

- Joe Gersch and Dan Massey


On Mar 5, 2012, at 7:08 PM, Terry Manderson wrote:

> from the draft in question:
>=20
> " We limit the scope of this internet draft to the prevention of =
origin
>   and sub-prefix hijacks -- a capability that can be implemented and
>   deployed in a reasonable time frame."
>=20
> I think SIDR has completed its work on this item.
>=20
> This looks to me like a fresh set of eyes on the problem.
>=20
> I'd be willing, if there is time on the grow agenda, to listen to what =
the
> authors are proposing and then reflect on the GROW v SIDR question.
>=20
> You may be right - it may be a SIDR item. But given the SIDR space =
right now
> seems to be focused on the interaction with and between routers I'm =
not sure
> presenting it in SIDR will be be good for either SIDR or the Authors.
> .. just saying is all..
>=20
> Cheers
> Terry
>=20
>=20
> On 6/03/12 11:48 AM, "Ronald Bonica" <rbonica@juniper.net> wrote:
>=20
>> Is it attempting to solve a problem which is also being worked in =
SIDR?
>>=20
>>                                                Ron
>>=20
>>> -----Original Message-----
>>> From: Terry Manderson [mailto:terry.manderson@icann.org]
>>> Sent: Monday, March 05, 2012 8:38 PM
>>> To: Christopher Morrow; Ronald Bonica
>>> Cc: grow@ietf.org
>>> Subject: Re: [GROW] Fwd: New Version Notification for draft-gersch-
>>> grow-revdns-bgp-00.txt
>>>=20
>>> =46rom my reading of the SIDR charter:
>>>=20
>>> " Building upon the already completed and implemented framework:
>>>=20
>>> * Resource Public Key Infrastructure (RPKI)
>>> * Distribution of RPKI data to routing devices and its use in
>>> operational networks
>>> * Document the use of certification objects within the secure =
routing
>>> architecture "
>>>=20
>>> I didn't see any RPKI use mentioned in revdns-bgp.
>>>=20
>>> So my guess is that if you went to present this at SIDR, most SIDR =
folk
>>> would say "it doesn't use RPKI" this is not the place. Irrespective =
of
>>> how flexible the chairs implement the charter under the allowances =
of
>>> the responsible AD.
>>>=20
>>> Cheers.
>>> T.
>>>=20
>>>=20
>>> On 6/03/12 11:31 AM, "Christopher Morrow"
>>> <christopher.morrow@gmail.com>
>>> wrote:
>>>=20
>>>> On Mon, Mar 5, 2012 at 8:12 PM, Ronald Bonica <rbonica@juniper.net>
>>> wrote:
>>>>> Chris,
>>>>>=20
>>>>> This draft appears to be operating in the same area as the origin
>>>>> authentication work that is currently progressing in SIDR. =
Shouldn't
>>>>> all of that work be in one place?
>>>>>=20
>>>>> My guess is that it belongs in SIDR.
>>>>=20
>>>> also was my guess, just looking for consensus on that I believe I
>>> was.
>>>>=20
>>>> -chris
>>>>=20
>>>>>                                                 Ron
>>>>>=20
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On
>>> Behalf
>>>>>> Of Christopher Morrow
>>>>>> Sent: Monday, March 05, 2012 4:22 PM
>>>>>> To: Joseph Gersch
>>>>>> Cc: grow@ietf.org
>>>>>> Subject: Re: [GROW] Fwd: New Version Notification for =
draft-gersch-
>>>>>> grow-revdns-bgp-00.txt
>>>>>>=20
>>>>>> It would be helpful to the chairs (at least) to get a sense of =
the
>>>>>> 'room' (list) on this topic, it seems that the focus is really on =
a
>>>>>> dnsops sort of paper, though interaction could be had in the
>>> routing
>>>>>> space as well (or that's an intent of the draft's work).
>>>>>>=20
>>>>>> It's not clear that GROW is the place for this work, but keeping
>>>>>> folks informed isn't a bad plan either (I think).
>>>>>>=20
>>>>>> -chris
>>>>>> (co-chair)
>>>>>>=20
>>>>>> On Tue, Feb 28, 2012 at 3:58 PM, Joseph Gersch
>>>>>> <joe.gersch@secure64.com> wrote:
>>>>>>> All,
>>>>>>>   we have submitted a new draft that we would like to present at
>>>>>>> the Paris IETF meeting.
>>>>>>> Please take the time to send any comments and suggestions
>>> regarding
>>>>>>> this idea on using records in  the reverse DNS to help secure =
BGP
>>>>>> route origins.
>>>>>>>=20
>>>>>>> Best regards,
>>>>>>>    - Joe Gersch, Dan Massey, Eric Osterweil and Lixia Zhang
>>>>>>>=20
>>>>>>> Begin forwarded message:
>>>>>>>=20
>>>>>>> From: internet-drafts@ietf.org
>>>>>>> Subject: New Version Notification for
>>>>>>> draft-gersch-grow-revdns-bgp-00.txt
>>>>>>> Date: February 28, 2012 1:51:59 PM MST
>>>>>>> To: joe.gersch@secure64.com
>>>>>>> Cc: lixia@cs.ucla.edu, eosterweil@verisign.com,
>>>>>>> massey@cs.colostate.edu
>>>>>>>=20
>>>>>>> A new version of I-D, draft-gersch-grow-revdns-bgp-00.txt has =
been
>>>>>>> successfully submitted by Joe Gersch and posted to the IETF
>>>>>> repository.
>>>>>>>=20
>>>>>>> Filename: draft-gersch-grow-revdns-bgp
>>>>>>> Revision: 00
>>>>>>> Title: DNS Resource Records for BGP Routing Data Creation date:
>>>>>>> 2012-02-29 WG ID: Individual Submission Number of pages: 22
>>>>>>>=20
>>>>>>> Abstract:
>>>>>>>   This draft proposes the creation of two DNS record types for
>>>>>> storing
>>>>>>>   BGP routing information in the reverse DNS.  The RLOCK record
>>>>>> allows
>>>>>>>   prefix owners to indicate whether the DNS is being used to
>>>>>>> publish
>>>>>>>   routing data.  The SRO record allows operators to indicate
>>>>>>> whether an
>>>>>>>   IPv4 or IPv6 prefix ought to appear in global routing tables =
and
>>>>>>>   identifies authorized origin Autonomous System Number(s) for
>>> that
>>>>>>>   prefix.  The published data can be used in a variety of =
contexts
>>>>>> and
>>>>>>>   can be extended to include additional information.  This work =
is
>>>>>>> part
>>>>>>>   of an on-going effort and is accessible in an active testbed.
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> The IETF Secretariat
>>>>>>>=20
>>>>>>>=20
>>>>>>> Joseph Gersch
>>>>>>> Chief Operating Officer
>>>>>>> Secure64 Software Corporation
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> GROW mailing list
>>>>>>> GROW@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/grow
>>>>>>>=20
>>>>>> _______________________________________________
>>>>>> GROW mailing list
>>>>>> GROW@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/grow
>>>> _______________________________________________
>>>> GROW mailing list
>>>> GROW@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/grow
>>=20
>=20
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

Joseph Gersch
Chief Operating Officer
Secure64 Software Corporation




From arturo.servin@gmail.com  Thu Mar 15 17:48:31 2012
Return-Path: <arturo.servin@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F49221E8035 for <grow@ietfa.amsl.com>; Thu, 15 Mar 2012 17:48:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 3BKQht08FKkf for <grow@ietfa.amsl.com>; Thu, 15 Mar 2012 17:48:30 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id F1F0221E800F for <grow@ietf.org>; Thu, 15 Mar 2012 17:48:24 -0700 (PDT)
Received: by pbbrq13 with SMTP id rq13so110171pbb.31 for <grow@ietf.org>; Thu, 15 Mar 2012 17:48:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=j4nR7qC6i0Hi3J25X3aXu9JowC90onm9ahyfhV5cdms=; b=j+P7yRsidOgZpQXs3rhbc0fgE9y9CWPZ2xwgt5dCuaOgQ3p6ksLPIhgSapIMDs5tfG LlGrQ0AuqNRikijiXmzzGZTs8mgo3Jk7h5R/V3s6E0a534+JoI8NbzOEIQxIGDTZdFjM jRvk6hHt+0PYgcD0vltolLV+XUl8dYIs1Ae5Hpg2wFizV81+uUYcng+QFt6XtIw5lHKS 7SgqBYIe7PemqjvQ86QI00JIubkKCe2CxaJu83SeUsNwV4y0tUwngLpeN8f1KBOYM1Zl j2awXnmvN0FBjU3HSsEBYPvEd010qLM00LYtEViFhjRMSgoL0ZBKF/cu+guRDxBpozeA 2Ibw==
Received: by 10.68.237.194 with SMTP id ve2mr9188843pbc.60.1331858904799; Thu, 15 Mar 2012 17:48:24 -0700 (PDT)
Received: from [10.196.232.94] ([199.91.194.1]) by mx.google.com with ESMTPS id 4sm2958281pbp.76.2012.03.15.17.48.21 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 15 Mar 2012 17:48:23 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Arturo Servin <arturo.servin@gmail.com>
In-Reply-To: <C4A95AAF-391A-452D-AD59-28A5F9DA546F@secure64.com>
Date: Thu, 15 Mar 2012 18:48:19 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <78EB68D3-7021-4562-A740-A2F68517B2A3@gmail.com>
References: <CB7BAEBE.2272B%terry.manderson@icann.org> <C4A95AAF-391A-452D-AD59-28A5F9DA546F@secure64.com>
To: Joseph Gersch <joe.gersch@secure64.com>
X-Mailer: Apple Mail (2.1257)
Cc: grow@ietf.org
Subject: Re: [GROW] New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 00:48:31 -0000

Joseph,


On 14 Mar 2012, at 10:13, Joseph Gersch wrote:

> This thread is raising two questions:
>   1) should the discussion be in GROW or SIDR?
>   2) hasn't this idea been discussed before
>=20
> --- Regarding the location for the draft,  the group presented =
arguments on both sides.    We believe that GROW is the proper place to =
lead the discussion.  However we have been invited to give a summary =
presentation at SIDR to ensure that all interested parties are aware of =
this proposal.  However, SIDR limits their scope to:   =20
>=20
>> * Is an Autonomous System (AS) authorized to originate an IP prefix=20=

>> * Is the AS-Path represented in the route the same as the path =
through=20
>> which the NLRI traveled=20
>=20
> Neither of these really fit our draft well.   You cannot use our =
approach to see all the prefixes that are authorized to originate from a =
given AS.   Instead of looking at prefix ranges or an AS,  this approach =
starts from a specific prefix and asks to identify its origin AS.   This =
is similar,  but not identical to what SIDR seeks to do.=20

	Validating a prefix using the origin ASN looks a lot to =
RPKI-Origin Validation.


>=20
> The second SIDR objective does not fit our work at all.    We do not =
seek to validate a complete many hop path.    In this sense, we don't =
fit SIDR.    As we mentioned above,  we are interested in getting =
comments from SIDR,  but we feel GROW is a better fit.    In addition,  =
we have an operational testbed and are working to get more participants =
in operations.   This is something people can participate in now.   So =
in this sense,  we were shooting for something we view as more of a =
routing operation issue and hence GROW. =20
>=20
> This proposal also impacts the DNSOP and DNSEXT groups.  We have asked =
people on those mailing lists for comments, and a presentation will be =
made at DNSOP as well.
>=20
> --- Regarding the "already discussed issue":
>   This earlier proposal was the T Bates / R Bush draft from 1998.  A =
lot of progress has taken place during the last 14 years.  The root zone =
and in-addr.arpa are signed with DNSSEC.   A naming convention for CIDR =
addresses in the reverse DNS is being proposed at DNSOP.   These new =
record types enable some interesting capabilities that are
> worth discussing at GROW. =20
>=20
> - Joe Gersch and Dan Massey


	As I mentioned before, I do not think this work belongs to GROW. =
I would rather prefer to see it in SIDR as a WG item and to be discussed =
in parallel here and DNSOP, but not the other way.

	In the end if your approach is to secure bgp, then secure IDR, =
then SIDR.=20

	Also, from SIDR charter I read:

"The two vulnerabilities that will be
  addressed are:

   * Is an Autonomous System (AS) authorized to originate an IP prefix

"

	Unless I understood wrongly your draft, I do not see why it does =
not fit SIDR's charter.


Regards,
.as




From rajiva@cisco.com  Thu Mar  8 11:59:58 2012
Return-Path: <rajiva@cisco.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9AF21E8039; Thu,  8 Mar 2012 11:59:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.434
X-Spam-Level: 
X-Spam-Status: No, score=-9.434 tagged_above=-999 required=5 tests=[AWL=0.565,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
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 Ae9MdGNTXjOe; Thu,  8 Mar 2012 11:59:57 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id C002421E802B; Thu,  8 Mar 2012 11:59:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rajiva@cisco.com; l=3320; q=dns/txt; s=iport; t=1331236798; x=1332446398; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to:cc; bh=RGvUbd1jdAg2WJv4JSzN0Eygy15JLQDqNRWwclJUTA0=; b=lYFrWv4Z6CqMix6FenggMvp0XwjCZftphJ9h5ToAhoByNzdnrGjnbhV/ p6VyaBPGRzfeBzD1mdMgxCMwmXBz0lYgd9/YzhX+Sdajw9MUZduklDzLG 7Se8BnFJb1T1WIz3F5AyR4Ij/i4cGcC8rqL1xg46P730Pa3CipWfc2NaK Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAH4OWU+tJXG//2dsb2JhbABDDrUbgQeCCgEBAQQBAQEPAR0KNAQHDAYBCBEEAQEBCgYXAQcmHwkJAQQBEggah2gLmz8Bnw6KKIVLYwSIUp0LgixWgT0
X-IronPort-AV: E=Sophos;i="4.73,553,1325462400"; d="scan'208";a="64925322"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-1.cisco.com with ESMTP; 08 Mar 2012 19:59:57 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core2-4.cisco.com (8.14.3/8.14.3) with ESMTP id q28Jxvrr008952;  Thu, 8 Mar 2012 19:59:57 GMT
Received: from xmb-rcd-111.cisco.com ([72.163.62.153]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 8 Mar 2012 13:59:57 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 8 Mar 2012 13:59:55 -0600
Message-ID: <067E6CE33034954AAC05C9EC85E2577C0795D53E@XMB-RCD-111.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] New Draft: Using Only Link-Local Address in Network Core
Thread-Index: Acz9U6RMQtPs5mv8S7uNO+xYhpWncgADegtwAAD6z8A=
From: "Rajiv Asati (rajiva)" <rajiva@cisco.com>
To: "George, Wes" <wesley.george@twcable.com>, "Chuck Anderson" <cra@WPI.EDU>,  <v6ops@ietf.org>, "AnthonyKirkham" <tkirkham@anthony-kirkham.com>
X-OriginalArrivalTime: 08 Mar 2012 19:59:57.0165 (UTC) FILETIME=[095049D0:01CCFD66]
X-Mailman-Approved-At: Thu, 22 Mar 2012 18:08:27 -0700
Cc: grow@ietf.org
Subject: Re: [GROW] [v6ops] New Draft: Using Only Link-Local Address in Network	Core
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 19:59:58 -0000

Hi Wes,

That draft (in GROW) is mostly for IPv4 network, not for IPv6 network.

Nonetheless, you have a point.   =20

Cheers
Rajiv=20


> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> Of George, Wes
> Sent: Thursday, March 08, 2012 2:34 PM
> To: Chuck Anderson; v6ops@ietf.org; AnthonyKirkham
> Cc: grow@ietf.org
> Subject: Re: [v6ops] New Draft: Using Only Link-Local Address in
Network
> Core
>=20
> The proposed comparison already pretty much exists within a draft
written
> and being adopted in GROW.
>=20
> http://tools.ietf.org/html/draft-kirkham-private-ip-sp-cores-02
>=20
>=20
> I'm thinking that perhaps the authors of the two drafts need to get
together
> and either bolster the discussion around IPv6 and link-local in the
current
> Kirkham draft, or turn this new draft into a companion document to
-kirkham
> so that we end up with two non-overlapping drafts, one that covers
IPv4 and
> one that covers IPv6 with a similar format.
>=20
> Thanks,
>=20
> Wes George
>=20
> > -----Original Message-----
> > From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On
Behalf
> Of
> > Chuck Anderson
> > Sent: Thursday, March 08, 2012 12:37 PM
> > To: v6ops@ietf.org
> > Subject: Re: [v6ops] New Draft: Using Only Link-Local Address in
Network
> Core
> >
>=20
> http://wiki.tools.ietf.org/html/draft-behringer-lla-only-00
>=20
> > On Thu, Mar 08, 2012 at 06:30:38PM +0100, Gert Doering wrote:
> > > > > Abstract
> > > > >
> > > > >   This document proposes to use only IPv6 link-local addresses
on
> > > > >   infrastructure links between routers, wherever possible.  It
> > > > >   discusses the advantages and disadvantages of this approach
to aide
> > > > >   the decision process for a given network,
> > >
> > > I'm perfectly fine with that abstract.  I just want to be sure
that
> > > this practice isn't advocated as a BCP to do so (because next
thing our
> > > customers or some crazy auditors will tell us that we do it all
wrong).
> >
> > Perhaps the draft could be reworked to be a comparison and overview
of
> > both techniques, LLA and global addressing, and their pros/cons
> > without having a position/recommendation/BCP for either method.
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
>=20
> This E-mail and any of its attachments may contain Time Warner Cable
> proprietary information, which is privileged, confidential, or subject
to
> copyright belonging to Time Warner Cable. This E-mail is intended
solely for
> the use of the individual or entity to which it is addressed. If you
are not the
> intended recipient of this E-mail, you are hereby notified that any
> dissemination, distribution, copying, or action taken in relation to
the
> contents of and attachments to this E-mail is strictly prohibited and
may be
> unlawful. If you have received this E-mail in error, please notify the
sender
> immediately and permanently delete the original and any copy of this
E-mail
> and any printout.
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From weiler@watson.org  Thu Mar 22 17:04:51 2012
Return-Path: <weiler@watson.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 218C721E803C for <grow@ietfa.amsl.com>; Thu, 22 Mar 2012 17:04:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.772
X-Spam-Level: 
X-Spam-Status: No, score=-1.772 tagged_above=-999 required=5 tests=[AWL=-0.662, BAYES_05=-1.11]
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 XZroga4fn77R for <grow@ietfa.amsl.com>; Thu, 22 Mar 2012 17:04:50 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by ietfa.amsl.com (Postfix) with ESMTP id 16C0121E8013 for <grow@ietf.org>; Thu, 22 Mar 2012 17:04:50 -0700 (PDT)
Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.4/8.14.4) with ESMTP id q2N04n1d038239; Thu, 22 Mar 2012 20:04:49 -0400 (EDT) (envelope-from weiler@watson.org)
Received: from localhost (weiler@localhost) by fledge.watson.org (8.14.4/8.14.4/Submit) with ESMTP id q2N04nsp038235; Thu, 22 Mar 2012 20:04:49 -0400 (EDT) (envelope-from weiler@watson.org)
X-Authentication-Warning: fledge.watson.org: weiler owned process doing -bs
Date: Thu, 22 Mar 2012 20:04:49 -0400 (EDT)
From: Samuel Weiler <weiler@watson.org>
To: grow@ietf.org
Message-ID: <alpine.BSF.2.00.1203222002570.35808@fledge.watson.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (fledge.watson.org [127.0.0.1]); Thu, 22 Mar 2012 20:04:49 -0400 (EDT)
X-Mailman-Approved-At: Thu, 22 Mar 2012 18:08:27 -0700
Subject: Re: [GROW] New Version Notification for draft-gersch-grow-revdns-bgp-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Mar 2012 00:04:51 -0000

First, my thanks to the authors for the very readable drafts.

The SIDR charter includes:

> * Is an Autonomous System (AS) authorized to originate an IP prefix

Joe Gersch and Dan Massey write:

> You cannot use our approach to see all the prefixes that are
> authorized to originate from a given AS.  Instead of looking at
> prefix ranges or an AS, this approach starts from a specific prefix
> and asks to identify its origin AS.  This is similar, but not
> identical to what SIDR seeks to do.

Actually, I think what you're doing is exactly what that line the SIDR
charter means, though I see how it could be confusing.  The RPKI does
not give a list of all prefixes that may be originated by an AS; it
answers the "which ASes" question for a given prefix, which is what
your proposal also seems to be aiming to do.

I think this clearly fits the SIDR charter.  (Indeed, your scheme
doesn't do anything for that second bullet in the SIDR charter re:
path protection, but that's okay.)

I think there are differences in the semantics of this v. the RPKI,
and I would love to see an analysis of the differences couched in the
language of sets.

And as for prior work, this is a novel enough variation to deserve 
some consideration.  In addition to the citations you already have, 
Bill Manning also did some work in this space; look for an INET'98 
paper.

-- Sam


From christopher.morrow@gmail.com  Sat Mar 24 08:04:08 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FE2321F86BD for <grow@ietfa.amsl.com>; Sat, 24 Mar 2012 08:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.556
X-Spam-Level: 
X-Spam-Status: No, score=-103.556 tagged_above=-999 required=5 tests=[AWL=0.043, 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 rFR4deY80OeS for <grow@ietfa.amsl.com>; Sat, 24 Mar 2012 08:04:08 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id E3AEC21F86B0 for <grow@ietf.org>; Sat, 24 Mar 2012 08:04:07 -0700 (PDT)
Received: by obbtb4 with SMTP id tb4so3970938obb.31 for <grow@ietf.org>; Sat, 24 Mar 2012 08:04:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=sVqIZMUdnT15nYVOQwWIKEb/VDA+VKWKMoEodtfkYYM=; b=MK1ZDqalHi4rzB++BfoqeyowoqRgWt36Om3WqZPY2hEA+LYIlnj2nx05idBq8xQ/aB 6cy95l+lnrTgm73nYJXLvyPJvqrOObSoKjFjBt3JFRHgv6YWlYheOzxDk99UDw6nXbG1 EqCVrCXeTtYc5K+82eicaTGW7MeDGVKs3eW1MjRJM7/oUaBsDhqGks9UZ93xK76VQd/k 8my3ziqVxn1uMRQOfZAt9VHSR6nahRcwSkFRtRITxsflQ4fYqqdloQVDVBpGFYFMVVfX E5XktYU6L3fFu7aDKCWMd7hkYzt8/88Y2teZ97+MebUA3tJfnwMocE0UXErhvLED2VUl 3i1Q==
MIME-Version: 1.0
Received: by 10.60.9.38 with SMTP id w6mr19028728oea.41.1332601447579; Sat, 24 Mar 2012 08:04:07 -0700 (PDT)
Received: by 10.182.80.137 with HTTP; Sat, 24 Mar 2012 08:04:07 -0700 (PDT)
In-Reply-To: <20120311204519.GH30627@slice>
References: <4E35F7CA.9000606@cisco.com> <20120311203715.GG30627@slice> <20120311204519.GH30627@slice>
Date: Sat, 24 Mar 2012 11:04:07 -0400
Message-ID: <CAL9jLabNJZR2EL8FiQEy5g8YUUiE6Yy1M5vsxw=JC=vd9H046w@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: grow@ietf.org, Anthony Kirkham <tkirkham@cisco.com>
Subject: Re: [GROW] How to progress - Private IP in SP Core
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Mar 2012 15:04:08 -0000

On Sun, Mar 11, 2012 at 4:45 PM, Jeffrey Haas <jhaas@pfrc.org> wrote:
> Sigh. =A0I replied to an item in an mis-sorted grow mailbox without check=
ing
> the date. =A0It looks like this was supported for WG adoption, but I stil=
l
> don't see a matching draft-grow?

we missed the draft 00 deadline, so Tony I think is sending (or has
sent?) one in anyway and it out to pop out the sausage manufacture
when the floodgates open.

> On Sun, Mar 11, 2012 at 04:37:15PM -0400, Jeffrey Haas wrote:
>> Tony,
>>
>> Note, I'm not speaking for the chairs or the ADs.
>>
>> On Mon, Aug 01, 2011 at 10:48:10AM +1000, Anthony Kirkham wrote:
>> > I'd appreciate any advice on how I might progress this draft. I'm
>> > reasonably happy with it now, but unsure how to take it the next
>> > step. I'd greatly appreciate any guidance.
>>
>> Two paths are:
>> - Keep it as an individual submission and find an AD to sponsor the
>> =A0 appropriate IESG review, etc:
>> =A0 http://www.ietf.org/iesg/statement/ad-sponsoring-docs.html
>> - Get the GROW chairs to do some of this work for you by requesting adop=
tion
>> =A0 of the draft as a GROW WG document. =A0Glancing at the *very stale* =
charter,
>> =A0 it's in scope for the WG. =A0IMO, given the amount of comment the dr=
aft has
>> =A0 received to date, perhaps it should even just go through WGLC.
>>
>> -- Jeff
>>
>> P.S. to the GROW chairs - it's probably time for a recharter. =A0And I t=
hought
>> the BFD milestones were stale! :-)
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

From internet-drafts@ietf.org  Tue Mar 27 01:35:34 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A361E21F88F3; Tue, 27 Mar 2012 01:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.4
X-Spam-Level: 
X-Spam-Status: No, score=-102.4 tagged_above=-999 required=5 tests=[AWL=-0.028, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, 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 zw1h0q0c1Tsm; Tue, 27 Mar 2012 01:35:34 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ED8821F88EA; Tue, 27 Mar 2012 01:35:34 -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: 4.00
Message-ID: <20120327083534.26710.594.idtracker@ietfa.amsl.com>
Date: Tue, 27 Mar 2012 01:35:34 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-03.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Mar 2012 08:35:34 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Global Routing Operations Working Gro=
up of the IETF.

	Title           : Operational Requirements for Enhanced Error Handling Beh=
aviour in BGP-4
	Author(s)       : Rob Shakir
	Filename        : draft-ietf-grow-ops-reqs-for-bgp-error-handling-03.txt
	Pages           : 27
	Date            : 2012-03-27

   BGP-4 is utilised as a key intra- and inter-Autonomous System routing
   protocol in modern IP networks.  The failure modes as defined by the
   original protocol standards are based on a number of assumptions
   around the impact of session failure.  Numerous incidents both in the
   global Internet routing table and within Service Provider networks
   have been caused by strict handling of a single invalid UPDATE
   message causing large-scale failures in one or more Autonomous
   Systems.

   This memo describes the current use of BGP-4 within Service Provider
   networks, and outlines a set of requirements for further work to
   enhance the mechanisms available to a BGP-4 implementation when
   erroneous data is detected.  Whilst this document does not provide
   specification of any standard, it is intended as an overview of a set
   of enhancements to BGP-4 to improve the protocol's robustness to suit
   its current deployment.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-ops-reqs-for-bgp-error-=
handling-03.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-grow-ops-reqs-for-bgp-error-h=
andling-03.txt


From tkirkham@anthony-kirkham.com  Wed Mar 28 03:23:15 2012
Return-Path: <tkirkham@anthony-kirkham.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5BA221F891D for <grow@ietfa.amsl.com>; Wed, 28 Mar 2012 03:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l1kEucnrPpRG for <grow@ietfa.amsl.com>; Wed, 28 Mar 2012 03:23:15 -0700 (PDT)
Received: from nschwmtas06p.mx.bigpond.com (nschwmtas06p.mx.bigpond.com [61.9.189.152]) by ietfa.amsl.com (Postfix) with ESMTP id B653B21F891C for <grow@ietf.org>; Wed, 28 Mar 2012 03:23:14 -0700 (PDT)
Received: from nschwcmgw07p ([61.9.190.167]) by nschwmtas06p.mx.bigpond.com with ESMTP id <20120328102312.KHOS20430.nschwmtas06p.mx.bigpond.com@nschwcmgw07p>;  Wed, 28 Mar 2012 10:23:12 +0000
Received: from Anthonys-MacBook-Pro.local ([124.187.92.14]) by nschwcmgw07p with BigPond Outbound id qyP91i00B0JbYsC01yPB3c; Wed, 28 Mar 2012 10:23:12 +0000
X-Authority-Analysis: v=2.0 cv=ZuNv2qHG c=1 sm=1 a=eckBsgz14t+FqcypcVY6Mg==:17 a=o_vTIyrCwosA:10 a=6zIsyWyiF64A:10 a=Ib5BsLsVyy8A:10 a=bVeADsv9IVkA:10 a=8nJEP1OIZ-IA:10 a=Tg0nUI2_AAAA:8 a=48vgC7mUAAAA:8 a=rSZANQtX3TOeRp59nYIA:9 a=lleXvhrhgdlNUmDDfnIA:7 a=wPNLvfGTeEIA:10 a=hGXPqodgTi4A:10 a=3ODoesluOjEA:10 a=lZB815dzVvQA:10 a=eckBsgz14t+FqcypcVY6Mg==:117
Message-ID: <4F72E68C.1000807@anthony-kirkham.com>
Date: Wed, 28 Mar 2012 20:23:08 +1000
From: Anthony Kirkham <tkirkham@anthony-kirkham.com>
Organization: Anthony-Kirkham.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120313 Thunderbird/11.0
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>
References: <4E35F7CA.9000606@cisco.com> <20120311203715.GG30627@slice> <20120311204519.GH30627@slice> <CAL9jLabNJZR2EL8FiQEy5g8YUUiE6Yy1M5vsxw=JC=vd9H046w@mail.gmail.com>
In-Reply-To: <CAL9jLabNJZR2EL8FiQEy5g8YUUiE6Yy1M5vsxw=JC=vd9H046w@mail.gmail.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org, Anthony Kirkham <tkirkham@cisco.com>
Subject: Re: [GROW] How to progress - Private IP in SP Core
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: tkirkham@anthony-kirkham.com
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2012 10:23:15 -0000

I have just uploaded "draft-ietf-grow-private-ip-sp-cores-00" on 
datatracker. It has sent me the full access URL email, but given the 
last time I thought it was all uploaded OK, and wasn't, I'd appreciate 
if someone could verify the upload was successful

Tony K


On 25/03/12 1:04 AM, Christopher Morrow wrote:
> On Sun, Mar 11, 2012 at 4:45 PM, Jeffrey Haas<jhaas@pfrc.org>  wrote:
>> Sigh.  I replied to an item in an mis-sorted grow mailbox without checking
>> the date.  It looks like this was supported for WG adoption, but I still
>> don't see a matching draft-grow?
> we missed the draft 00 deadline, so Tony I think is sending (or has
> sent?) one in anyway and it out to pop out the sausage manufacture
> when the floodgates open.
>
>> On Sun, Mar 11, 2012 at 04:37:15PM -0400, Jeffrey Haas wrote:
>>> Tony,
>>>
>>> Note, I'm not speaking for the chairs or the ADs.
>>>
>>> On Mon, Aug 01, 2011 at 10:48:10AM +1000, Anthony Kirkham wrote:
>>>> I'd appreciate any advice on how I might progress this draft. I'm
>>>> reasonably happy with it now, but unsure how to take it the next
>>>> step. I'd greatly appreciate any guidance.
>>> Two paths are:
>>> - Keep it as an individual submission and find an AD to sponsor the
>>>    appropriate IESG review, etc:
>>>    http://www.ietf.org/iesg/statement/ad-sponsoring-docs.html
>>> - Get the GROW chairs to do some of this work for you by requesting adoption
>>>    of the draft as a GROW WG document.  Glancing at the *very stale* charter,
>>>    it's in scope for the WG.  IMO, given the amount of comment the draft has
>>>    received to date, perhaps it should even just go through WGLC.
>>>
>>> -- Jeff
>>>
>>> P.S. to the GROW chairs - it's probably time for a recharter.  And I thought
>>> the BFD milestones were stale! :-)
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
>


-- 



From internet-drafts@ietf.org  Wed Mar 28 04:21:31 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2BF421E8019; Wed, 28 Mar 2012 04:21:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.545
X-Spam-Level: 
X-Spam-Status: No, score=-102.545 tagged_above=-999 required=5 tests=[AWL=0.054, 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 cqKiaKyM0JEX; Wed, 28 Mar 2012 04:21:28 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3645021E8097; Wed, 28 Mar 2012 04:21:28 -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: 4.00
Message-ID: <20120328112128.19122.59432.idtracker@ietfa.amsl.com>
Date: Wed, 28 Mar 2012 04:21:28 -0700
Cc: grow@ietf.org
Subject: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2012 11:21:31 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Global Routing Operations Working Gro=
up of the IETF.

	Title           : Issues with Private IP Addressing in the Internet
	Author(s)       : Anthony Kirkham
	Filename        : draft-ietf-grow-private-ip-sp-cores-00.txt
	Pages           : 15
	Date            : 2012-03-28

   The purpose of this document is to provide a discussion of the
   potential problems of using private, RFC1918, or non-globally-
   routable addressing within the core of an SP network.  The discussion
   focuses on link addresses and to a small extent loopback addresses.
   While many of the issues are well recognised within the ISP
   community, there appears to be no document that collectively
   describes the issues.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-00.=
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-grow-private-ip-sp-cores-00.t=
xt


From christopher.morrow@gmail.com  Wed Mar 28 04:22:57 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7326621F88F4 for <grow@ietfa.amsl.com>; Wed, 28 Mar 2012 04:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.576
X-Spam-Level: 
X-Spam-Status: No, score=-103.576 tagged_above=-999 required=5 tests=[AWL=0.023, 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 M6XXSyEpFZ4Y for <grow@ietfa.amsl.com>; Wed, 28 Mar 2012 04:22:56 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3531D21F8892 for <grow@ietf.org>; Wed, 28 Mar 2012 04:22:52 -0700 (PDT)
Received: by obbtb4 with SMTP id tb4so1432653obb.31 for <grow@ietf.org>; Wed, 28 Mar 2012 04:22:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=bCPb78oAg67j47MgUx6kwcbVUaCnOOTmrje+BPYAAZM=; b=htKxqQtos8XblgAAc+e/daYV30r7rpx7HF0WalusrUeJCq2c1TsYTaWpUDyqdX3CHx X8LvrKSlV4a9ebrg7v3RwQxvlp6LFSYdv+yzppZ6IUuN7TdUHAuLfuKtTKpEt5SxY+/R IIYhwKyu5vEG/BRRREKzc0OGpKurqyzwPx1Dt252FQLjicz/gsZc9WFLEhKb2sPb2lXG FYPVIr9WfzDNyHgalzNvcxETHK1o7jcjQ/C28RlzfLxwXeLxa67B9Egz8lFcv1Y8nN+h BqHS04lE0Ooyd+CJG/3punO1NS1uruh0rFStRVBbpBpiPgC4XjzTkIBVisccqVC08sb9 W8Fw==
MIME-Version: 1.0
Received: by 10.182.155.68 with SMTP id vu4mr36813606obb.61.1332933771804; Wed, 28 Mar 2012 04:22:51 -0700 (PDT)
Received: by 10.182.80.137 with HTTP; Wed, 28 Mar 2012 04:22:51 -0700 (PDT)
In-Reply-To: <4F72E68C.1000807@anthony-kirkham.com>
References: <4E35F7CA.9000606@cisco.com> <20120311203715.GG30627@slice> <20120311204519.GH30627@slice> <CAL9jLabNJZR2EL8FiQEy5g8YUUiE6Yy1M5vsxw=JC=vd9H046w@mail.gmail.com> <4F72E68C.1000807@anthony-kirkham.com>
Date: Wed, 28 Mar 2012 07:22:51 -0400
Message-ID: <CAL9jLaaDrG59t4UvC7W60Vw7bsDoFY-NDkvi+N0HLQuBUN+y6Q@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: tkirkham@anthony-kirkham.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: grow@ietf.org, Anthony Kirkham <tkirkham@cisco.com>
Subject: Re: [GROW] How to progress - Private IP in SP Core
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2012 11:22:57 -0000

On Wed, Mar 28, 2012 at 6:23 AM, Anthony Kirkham
<tkirkham@anthony-kirkham.com> wrote:
>
> I have just uploaded "draft-ietf-grow-private-ip-sp-cores-00" on
> datatracker. It has sent me the full access URL email, but given the last
> time I thought it was all uploaded OK, and wasn't, I'd appreciate if some=
one
> could verify the upload was successful

I approved the submit, congrats!

> Tony K
>
>
>
> On 25/03/12 1:04 AM, Christopher Morrow wrote:
>>
>> On Sun, Mar 11, 2012 at 4:45 PM, Jeffrey Haas<jhaas@pfrc.org> =A0wrote:
>>>
>>> Sigh. =A0I replied to an item in an mis-sorted grow mailbox without
>>> checking
>>> the date. =A0It looks like this was supported for WG adoption, but I st=
ill
>>> don't see a matching draft-grow?
>>
>> we missed the draft 00 deadline, so Tony I think is sending (or has
>> sent?) one in anyway and it out to pop out the sausage manufacture
>> when the floodgates open.
>>
>>> On Sun, Mar 11, 2012 at 04:37:15PM -0400, Jeffrey Haas wrote:
>>>>
>>>> Tony,
>>>>
>>>> Note, I'm not speaking for the chairs or the ADs.
>>>>
>>>> On Mon, Aug 01, 2011 at 10:48:10AM +1000, Anthony Kirkham wrote:
>>>>>
>>>>> I'd appreciate any advice on how I might progress this draft. I'm
>>>>> reasonably happy with it now, but unsure how to take it the next
>>>>> step. I'd greatly appreciate any guidance.
>>>>
>>>> Two paths are:
>>>> - Keep it as an individual submission and find an AD to sponsor the
>>>> =A0 appropriate IESG review, etc:
>>>> =A0 http://www.ietf.org/iesg/statement/ad-sponsoring-docs.html
>>>> - Get the GROW chairs to do some of this work for you by requesting
>>>> adoption
>>>> =A0 of the draft as a GROW WG document. =A0Glancing at the *very stale=
*
>>>> charter,
>>>> =A0 it's in scope for the WG. =A0IMO, given the amount of comment the =
draft
>>>> has
>>>> =A0 received to date, perhaps it should even just go through WGLC.
>>>>
>>>> -- Jeff
>>>>
>>>> P.S. to the GROW chairs - it's probably time for a recharter. =A0And I
>>>> thought
>>>> the BFD milestones were stale! :-)
>>>> _______________________________________________
>>>> GROW mailing list
>>>> GROW@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/grow
>>>
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
>>
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>
>>
>
>
> --
>
>

From robert@raszuk.net  Fri Mar 30 03:44:45 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 450ED21F867B for <grow@ietfa.amsl.com>; Fri, 30 Mar 2012 03:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.314
X-Spam-Level: 
X-Spam-Status: No, score=-2.314 tagged_above=-999 required=5 tests=[AWL=0.285,  BAYES_00=-2.599]
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 SbbEf-omqnAq for <grow@ietfa.amsl.com>; Fri, 30 Mar 2012 03:44:44 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 6E49221F8675 for <grow@ietf.org>; Fri, 30 Mar 2012 03:44:44 -0700 (PDT)
Received: (qmail 21248 invoked by uid 399); 30 Mar 2012 10:44:43 -0000
Received: from unknown (HELO ?130.129.22.61?) (pbs:robert@raszuk.net@130.129.22.61) by mail1310.opentransfer.com with ESMTPM; 30 Mar 2012 10:44:43 -0000
X-Originating-IP: 130.129.22.61
Message-ID: <4F758E9E.2030006@raszuk.net>
Date: Fri, 30 Mar 2012 12:44:46 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: Peter Schoenmaker <pds@lugs.com>,  Christopher Morrow <christopher.morrow@gmail.com>
References: <CAL9jLaYdpdW5gmj3WdssRPFTO74RNxMkHVTa0U-MNv9oVPN6wQ@mail.gmail.com> <AAB61917-E5E4-40A9-8FC6-38D6DFCF1668@cw.com>
In-Reply-To: <AAB61917-E5E4-40A9-8FC6-38D6DFCF1668@cw.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WG Adoption call for:draft-hilliard-ix-bgp-route-server-operations
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 10:44:45 -0000

Chairs,

What is the status of route-server-operations draft ? We had some 
acceptances in the GROW WG meeting and on the list before, but we never 
saw official approvals to resubmit as official GROW WG document.

Many thx,
R.

> Hi Chris, GROW,
>
> I'd like to voice my support for this draft's adoption by GROW - it
> seems to me that there are particular complexities of operating route
> servers at IXPs well, and their stability and functionality is of
> particular interest to Internet network operators - making this draft
> very relevant for this group.
>
> Kind regards, r.
>
> Sent from my iPad
>
> On 17 Nov 2011, at 07:55, "Christopher
> Morrow"<christopher.morrow@gmail.com>  wrote:
>
>> Pursuant to the WG meeting discussion, this is a split part of the
>> original routeservers document, we'd like to poll the group for WG
>> Adoption at this time.
>>
>> <http://tools.ietf.org/html?draft=draft-hilliard-ix-bgp-route-server-operations>
>>
>>
>>
Please have a read through and let us know on-list about applicability
>> to this group in particular. Call closes 12/01/2011 (dec 01 2011
>> for the non-us-based folks)
>>
>> -Chris (co-chair) _______________________________________________
>> GROW mailing list GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow


From christopher.morrow@gmail.com  Fri Mar 30 03:46:48 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55DB821F86B1 for <grow@ietfa.amsl.com>; Fri, 30 Mar 2012 03:46:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.582
X-Spam-Level: 
X-Spam-Status: No, score=-103.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 T4y4jwjeenyw for <grow@ietfa.amsl.com>; Fri, 30 Mar 2012 03:46:47 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id C39A921F86BB for <grow@ietf.org>; Fri, 30 Mar 2012 03:46:47 -0700 (PDT)
Received: by obbta17 with SMTP id ta17so956573obb.31 for <grow@ietf.org>; Fri, 30 Mar 2012 03:46:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=mORS5/3rVrhT2E81f7XCVJ1moIVKBgL6fAVg8UMh9M4=; b=CJwq+4pUw9e9l9N+j1mMsBRmRTqtyYZ8h3SYIV2j9+d4GffMA5chSFmqUgfLAjB/Qo HdbgtVVJjIibhyuNAQyJVbhsvEl91KMYlSwh/7IcNE3YmiLpIwI4sAPitpuVtv3F5YC+ XNgc2USCfgV7ru8ofqQ9PxeFBDAfgWRtw8KSRAgCzssXVdYzDArzHp7CSLdrjo7n1eiY a77bObzWtR70Q/jENzW107+uy/6kMXrfwhm8IZI/gGvAt+sKDDZ5ivPXqsrj8tqVKuTX t0/y/Y5uTn6BI5j/3TxBzXV4rmmivXW+KZbId+hDyXAM8hnybHaD6wxjE4OCH1BUqDTh 6bIA==
MIME-Version: 1.0
Received: by 10.60.1.7 with SMTP id 7mr1979205oei.71.1333104407384; Fri, 30 Mar 2012 03:46:47 -0700 (PDT)
Received: by 10.182.80.137 with HTTP; Fri, 30 Mar 2012 03:46:47 -0700 (PDT)
In-Reply-To: <4F758E9E.2030006@raszuk.net>
References: <CAL9jLaYdpdW5gmj3WdssRPFTO74RNxMkHVTa0U-MNv9oVPN6wQ@mail.gmail.com> <AAB61917-E5E4-40A9-8FC6-38D6DFCF1668@cw.com> <4F758E9E.2030006@raszuk.net>
Date: Fri, 30 Mar 2012 06:46:47 -0400
Message-ID: <CAL9jLaZ-3AyGugeeVnCHWLP7gOe7CkkSfR6Gu2rsSpOM6j-uXw@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
To: robert@raszuk.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: grow@ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WG Adoption call for:draft-hilliard-ix-bgp-route-server-operations
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 10:46:48 -0000

we had only 2 notes about it, both positive....
could we have a little more chat about it pls? 2 people is not
necessarily a consensus...

On Fri, Mar 30, 2012 at 6:44 AM, Robert Raszuk <robert@raszuk.net> wrote:
> Chairs,
>
> What is the status of route-server-operations draft ? We had some
> acceptances in the GROW WG meeting and on the list before, but we never s=
aw
> official approvals to resubmit as official GROW WG document.
>
> Many thx,
> R.
>
>
>> Hi Chris, GROW,
>>
>> I'd like to voice my support for this draft's adoption by GROW - it
>> seems to me that there are particular complexities of operating route
>> servers at IXPs well, and their stability and functionality is of
>> particular interest to Internet network operators - making this draft
>> very relevant for this group.
>>
>> Kind regards, r.
>>
>> Sent from my iPad
>>
>> On 17 Nov 2011, at 07:55, "Christopher
>> Morrow"<christopher.morrow@gmail.com> =A0wrote:
>>
>>> Pursuant to the WG meeting discussion, this is a split part of the
>>> original routeservers document, we'd like to poll the group for WG
>>> Adoption at this time.
>>>
>>>
>>> <http://tools.ietf.org/html?draft=3Ddraft-hilliard-ix-bgp-route-server-=
operations>
>>>
>>>
>>>
> Please have a read through and let us know on-list about applicability
>>>
>>> to this group in particular. Call closes 12/01/2011 (dec 01 2011
>>> for the non-us-based folks)
>>>
>>> -Chris (co-chair) _______________________________________________
>>> GROW mailing list GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
>
>

From robert@raszuk.net  Fri Mar 30 03:51:50 2012
Return-Path: <robert@raszuk.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9542521F8731 for <grow@ietfa.amsl.com>; Fri, 30 Mar 2012 03:51:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599]
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 j5YCWUW4gbdH for <grow@ietfa.amsl.com>; Fri, 30 Mar 2012 03:51:50 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id A50FD21F8712 for <grow@ietf.org>; Fri, 30 Mar 2012 03:51:49 -0700 (PDT)
Received: (qmail 784 invoked by uid 399); 30 Mar 2012 10:51:49 -0000
Received: from unknown (HELO ?130.129.22.61?) (pbs:robert@raszuk.net@130.129.22.61) by mail1310.opentransfer.com with ESMTPM; 30 Mar 2012 10:51:49 -0000
X-Originating-IP: 130.129.22.61
Message-ID: <4F759048.70601@raszuk.net>
Date: Fri, 30 Mar 2012 12:51:52 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>
References: <CAL9jLaYdpdW5gmj3WdssRPFTO74RNxMkHVTa0U-MNv9oVPN6wQ@mail.gmail.com> <AAB61917-E5E4-40A9-8FC6-38D6DFCF1668@cw.com> <4F758E9E.2030006@raszuk.net> <CAL9jLaZ-3AyGugeeVnCHWLP7gOe7CkkSfR6Gu2rsSpOM6j-uXw@mail.gmail.com>
In-Reply-To: <CAL9jLaZ-3AyGugeeVnCHWLP7gOe7CkkSfR6Gu2rsSpOM6j-uXw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org, grow-chairs@tools.ietf.org
Subject: Re: [GROW] WG Adoption call for:draft-hilliard-ix-bgp-route-server-operations
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 10:51:50 -0000

Hello Chris,

There was a bit more support both on the list and in the meetings for 
Route Servers. But it was under different name 
draft-jasinska-ix-bgp-route-server. Then IDR/GROW chairs decided to 
split the documents and now what is left in GROW is 
draft-hilliard-ix-bgp-route-server-operations.

The other draft went to IDR and is an IDR WG doc: 
draft-ietf-idr-ix-bgp-route-server since 26th of March.

Many thx,
R.

> we had only 2 notes about it, both positive....
> could we have a little more chat about it pls? 2 people is not
> necessarily a consensus...
>
> On Fri, Mar 30, 2012 at 6:44 AM, Robert Raszuk<robert@raszuk.net>  wrote:
>> Chairs,
>>
>> What is the status of route-server-operations draft ? We had some
>> acceptances in the GROW WG meeting and on the list before, but we never saw
>> official approvals to resubmit as official GROW WG document.
>>
>> Many thx,
>> R.
>>
>>
>>> Hi Chris, GROW,
>>>
>>> I'd like to voice my support for this draft's adoption by GROW - it
>>> seems to me that there are particular complexities of operating route
>>> servers at IXPs well, and their stability and functionality is of
>>> particular interest to Internet network operators - making this draft
>>> very relevant for this group.
>>>
>>> Kind regards, r.
>>>
>>> Sent from my iPad
>>>
>>> On 17 Nov 2011, at 07:55, "Christopher
>>> Morrow"<christopher.morrow@gmail.com>    wrote:
>>>
>>>> Pursuant to the WG meeting discussion, this is a split part of the
>>>> original routeservers document, we'd like to poll the group for WG
>>>> Adoption at this time.
>>>>
>>>>
>>>> <http://tools.ietf.org/html?draft=draft-hilliard-ix-bgp-route-server-operations>
>>>>
>>>>
>>>>
>> Please have a read through and let us know on-list about applicability
>>>>
>>>> to this group in particular. Call closes 12/01/2011 (dec 01 2011
>>>> for the non-us-based folks)
>>>>
>>>> -Chris (co-chair) _______________________________________________
>>>> GROW mailing list GROW@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/grow
>>
>>
>
>


From ietfc@btconnect.com  Fri Mar 30 04:41:34 2012
Return-Path: <ietfc@btconnect.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F2A221F87ED for <grow@ietfa.amsl.com>; Fri, 30 Mar 2012 04:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.064
X-Spam-Level: 
X-Spam-Status: No, score=-2.064 tagged_above=-999 required=5 tests=[AWL=0.535,  BAYES_00=-2.599]
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 JIvHngzy7mEs for <grow@ietfa.amsl.com>; Fri, 30 Mar 2012 04:41:33 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr06.btconnect.com [213.123.26.184]) by ietfa.amsl.com (Postfix) with ESMTP id 071BF21F87EB for <grow@ietf.org>; Fri, 30 Mar 2012 04:41:32 -0700 (PDT)
Received: from host86-162-135-195.range86-162.btcentralplus.com (HELO pc6) ([86.162.135.195]) by c2beaomr06.btconnect.com with SMTP id HBS78113; Fri, 30 Mar 2012 12:41:29 +0100 (BST)
Message-ID: <000901cd0e61$7efdef00$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Christopher Morrow" <christopher.morrow@gmail.com>, <tkirkham@anthony-kirkham.com>
References: <4E35F7CA.9000606@cisco.com> <20120311203715.GG30627@slice><20120311204519.GH30627@slice><CAL9jLabNJZR2EL8FiQEy5g8YUUiE6Yy1M5vsxw=JC=vd9H046w@mail.gmail.com><4F72E68C.1000807@anthony-kirkham.com> <CAL9jLaaDrG59t4UvC7W60Vw7bsDoFY-NDkvi+N0HLQuBUN+y6Q@mail.gmail.com>
Date: Fri, 30 Mar 2012 12:40:07 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4F759BE8.00AC, actions=TAG
X-Junkmail-Premium-Raw: score=8/50, refid=2.7.2:2012.3.30.105124:17:8.317, ip=86.162.135.195, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __MULTIPLE_RCPTS_CC_X2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __FRAUD_BODY_WEBMAIL, __CP_URI_IN_BODY, BODY_SIZE_4000_4999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, MULTIPLE_RCPTS, RDNS_SUSP, __FRAUD_WEBMAIL, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr06.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0201.4F759BE9.00CC,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
Cc: grow@ietf.org, Anthony Kirkham <tkirkham@cisco.com>
Subject: Re: [GROW] How to progress - Private IP in SP Core
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 11:41:34 -0000

----- Original Message -----
From: "Christopher Morrow" <christopher.morrow@gmail.com>
To: <tkirkham@anthony-kirkham.com>
Cc: <grow@ietf.org>; "Anthony Kirkham" <tkirkham@cisco.com>
Sent: Wednesday, March 28, 2012 1:22 PM
On Wed, Mar 28, 2012 at 6:23 AM, Anthony Kirkham
<tkirkham@anthony-kirkham.com> wrote:
>
> I have just uploaded "draft-ietf-grow-private-ip-sp-cores-00" on
> datatracker. It has sent me the full access URL email, but given the last
> time I thought it was all uploaded OK, and wasn't, I'd appreciate if someone
> could verify the upload was successful

I approved the submit, congrats!

<tp>
Yippee

I would suggest changing the normative reference to
bdgks-arin-shared-transition-space]
since that is now expired and so would delay things.
draft-weil
is in the RFC Editor's queue so that is ok.

Perhaps
OLD
 To address this scenario and others, at the time of writing, work was
   in progress to obtain a dedicated /10 address block for the purpose
   of Shared CGN (Carrier Grade NAT) Address Space.  Please refer to
   [bdgks-arin-shared-transition-space] and [weil-shared-transition-
   space-request] for details.  The purpose of Shared CGN Address Space
   is to number CPE (Customer Premise Equipment) interfaces that connect
   to CGN devices.  As explained in [weil-shared-transition-space-
   request], RFC1918 addressing has issues when used in this deployment
   scenario.

NEW
 To address this scenario and others, the IETF has allocated a dedicated /10
address block for the purpose
   of Shared CGN (Carrier Grade NAT) Address Space.  Please refer to
[weil-shared-transition-
   space-request] for details.  The purpose of Shared CGN Address Space
   is to number CPE (Customer Premise Equipment) interfaces that connect
   to CGN devices.  As explained in [weil-shared-transition-space-
   request], RFC1918 addressing has issues when used in this deployment
   scenario.

Tom Petch


> Tony K
>
>
>
> On 25/03/12 1:04 AM, Christopher Morrow wrote:
>>
>> On Sun, Mar 11, 2012 at 4:45 PM, Jeffrey Haas<jhaas@pfrc.org> wrote:
>>>
>>> Sigh. I replied to an item in an mis-sorted grow mailbox without
>>> checking
>>> the date. It looks like this was supported for WG adoption, but I still
>>> don't see a matching draft-grow?
>>
>> we missed the draft 00 deadline, so Tony I think is sending (or has
>> sent?) one in anyway and it out to pop out the sausage manufacture
>> when the floodgates open.
>>
>>> On Sun, Mar 11, 2012 at 04:37:15PM -0400, Jeffrey Haas wrote:
>>>>
>>>> Tony,
>>>>
>>>> Note, I'm not speaking for the chairs or the ADs.
>>>>
>>>> On Mon, Aug 01, 2011 at 10:48:10AM +1000, Anthony Kirkham wrote:
>>>>>
>>>>> I'd appreciate any advice on how I might progress this draft. I'm
>>>>> reasonably happy with it now, but unsure how to take it the next
>>>>> step. I'd greatly appreciate any guidance.
>>>>
>>>> Two paths are:
>>>> - Keep it as an individual submission and find an AD to sponsor the
>>>> appropriate IESG review, etc:
>>>> http://www.ietf.org/iesg/statement/ad-sponsoring-docs.html
>>>> - Get the GROW chairs to do some of this work for you by requesting
>>>> adoption
>>>> of the draft as a GROW WG document. Glancing at the *very stale*
>>>> charter,
>>>> it's in scope for the WG. IMO, given the amount of comment the draft
>>>> has
>>>> received to date, perhaps it should even just go through WGLC.
>>>>
>>>> -- Jeff
>>>>
>>>> P.S. to the GROW chairs - it's probably time for a recharter. And I
>>>> thought
>>>> the BFD milestones were stale! :-)
>>>> _______________________________________________
>>>> GROW mailing list
>>>> GROW@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/grow
>>>
>>> _______________________________________________
>>> GROW mailing list
>>> GROW@ietf.org
>>> https://www.ietf.org/mailman/listinfo/grow
>>
>> _______________________________________________
>> GROW mailing list
>> GROW@ietf.org
>> https://www.ietf.org/mailman/listinfo/grow
>>
>>
>
>
> --
>
>
_______________________________________________
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow



From wesley.george@twcable.com  Fri Mar 30 16:15:02 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6F6021F8691; Fri, 30 Mar 2012 16:15:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.259
X-Spam-Level: 
X-Spam-Status: No, score=-0.259 tagged_above=-999 required=5 tests=[AWL=-0.396, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6]
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 T47BktuRgJ47; Fri, 30 Mar 2012 16:15:01 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 766B221F8688; Fri, 30 Mar 2012 16:15:01 -0700 (PDT)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.75,346,1330923600"; d="scan'208";a="345186175"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 30 Mar 2012 19:15:00 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Fri, 30 Mar 2012 19:15:00 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "grow@ietf.org" <grow@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Date: Fri, 30 Mar 2012 19:14:58 -0400
Thread-Topic: draft-behringer-lla-only and draft-ietf-grow-private-ip-sp-cores
Thread-Index: Ac0M1PTc8z4ZGA26S5W5umLx5IqzdwB6fdhw
Message-ID: <DCC302FAA9FE5F4BBA4DCAD465693779173D6E9C51@PRVPEXVS03.corp.twcable.com>
References: <20120328112128.19122.59432.idtracker@ietfa.amsl.com>
In-Reply-To: <20120328112128.19122.59432.idtracker@ietfa.amsl.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
Cc: "draft-behringer-lla-only@tools.ietf.org" <draft-behringer-lla-only@tools.ietf.org>
Subject: [GROW] draft-behringer-lla-only and draft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 23:15:03 -0000

Cross-posting to both lists again because I was unable to attend the v6ops =
session where draft-behringer was discussed, draft-ietf-grow-private-ip-sp-=
cores is likely nearing WGLC, and I believe that the issue I raised needs t=
o be addressed before either proceeds. I defer to the chairs of both groups=
 to determine how to manage this across the two groups.

After reviewing both draft-grow-private-ip-sp-cores (Kirkham) and draft-beh=
ringer-lla-only again, I am even more convinced that they either need to be=
 merged, or that draft-behringer needs to be abandoned altogether as a bad =
idea. Draft-grow-private-ip-sp-cores is quite a lot more complete in its di=
scussion of the considerations around private IP usage, but focuses on IPv4=
, meaning that it *is* incomplete for lack of discussion of IPv6, which is =
a reality in most SP cores today. Nearly all of the same considerations app=
ly for IPv4 and IPv6 in this case, so there are probably a limited number o=
f changes that would be necessary to cover IPv6 in the Kirkham document.
I think that we need to come to some consensus on the recommended behavior =
on both cases. If the recommendation is different for one versus the other,=
 we need to have a unified and clear articulation as to why this is the cas=
e. It may be that the consensus is to not recommend a behavior at all, and =
simply expand the format of Kirkham's document to cover any IPv6-specific i=
tems, since it discusses pros and cons evenly (as an informational doc) rat=
her than recommending anything as a BCP. My vote is to do this, as I am unc=
onvinced that use of LLA represents BCP today, nor should it. I outline som=
e reasons below, but that's probably not as critical if others agree that t=
his is the proper method to proceed with these documents.



If draft-behringer is left as a separate document, here are some specific c=
omments:
The advantages proposed in draft-behringer are IMO not enough to justify re=
commending use of LLA.
- Smaller routing tables can be achieved through other methods such as sett=
ing the interfaces into passive mode in the IGP (so that they are not redis=
tributed into the IGP) and/or not redistributing connected routes. Further,=
 as SPs make great use of interface bundling (LAG), the number of interface=
s with IP addresses is dramatically reduced, making the need to pull the po=
int to point interfaces out of the routing table significantly lower.
- Reduced attack surface - draft-ietf-grow-private-ip-sp-cores sections 10 =
and 11 discuss this in great detail, and come to the conclusion that it is =
of limited benefit, and that alternatives exist to protect the infrastructu=
re.
- lower configuration complexity - while this is true, it is replaced by ad=
ditional complexity in troubleshooting. In the case of traces and pings loc=
ally on the box, it adds the additional step of requiring the operator to u=
se extended ping and trace commands to specify the exit interface in order =
to make the ping work (vs simply issuing "ping [ip address]"), and makes it=
 nearly impossible to derive the address of the remote interface without de=
termining the remote side router through some other means and logging into =
the router to look. (vs practice today of using an IP in the same subnet, u=
sually 1 digit up or down that can be guessed to save time).
- less address space: The other draft mentions this as well, in the context=
 of IPv4 where it might make a difference, but this simply is not much of a=
 concern with IPv6. An entire network could be numbered many times over out=
 of one /64.
-simpler DNS : Most ISPs operating at the scale where this makes any differ=
ence at all have tools to build the DNS forward and reverse entries for the=
ir infrastructure automatically based on the router name and interface name=
 extracted from their inventory tools. It's a few bits of scripting, so it'=
s not like having less interfaces in DNS results in any net reduction in wo=
rk or increase in the possibility of mistakes.

- Draft-ietf-grow-private-ip-sp-cores rightly notes that the proposed solut=
ion to broken pings/traces/PMTUD from draft-behringer (RFC 5837) has little=
 or no implementation. This makes it a hard sell as any sort of recommended=
 solution unless the benefits are much more significant than what is curren=
tly discussed in draft-behringer. This has to be a large enough benefit to =
justify pushing hard on router vendors to implement the feature and SPs to =
certify and deploy the code, and frankly there are many more important feat=
ures to consider.

Thanks,

Wes George


> -----Original Message-----
> From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: Wednesday, March 28, 2012 7:21 AM
> To: i-d-announce@ietf.org
> Cc: grow@ietf.org
> Subject: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-00.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the Global Routing Operations
> Working Group of the IETF.
>
>       Title           : Issues with Private IP Addressing in the Internet
>       Author(s)       : Anthony Kirkham
>       Filename        : draft-ietf-grow-private-ip-sp-cores-00.txt
>       Pages           : 15
>       Date            : 2012-03-28
>
>    The purpose of this document is to provide a discussion of the
>    potential problems of using private, RFC1918, or non-globally-
>    routable addressing within the core of an SP network.  The discussion
>    focuses on link addresses and to a small extent loopback addresses.
>    While many of the issues are well recognised within the ISP
>    community, there appears to be no document that collectively
>    describes the issues.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-0=
0.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-grow-private-ip-sp-cores-00=
.txt
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From ietfc@btconnect.com  Sat Mar 31 04:27:49 2012
Return-Path: <ietfc@btconnect.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3E6221F86B7; Sat, 31 Mar 2012 04:27:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.823
X-Spam-Level: 
X-Spam-Status: No, score=-1.823 tagged_above=-999 required=5 tests=[AWL=0.176,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 WD+qrr16GYAC; Sat, 31 Mar 2012 04:27:49 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr07.btconnect.com [213.123.26.185]) by ietfa.amsl.com (Postfix) with ESMTP id 076E521F86A8; Sat, 31 Mar 2012 04:27:45 -0700 (PDT)
Received: from host86-162-135-195.range86-162.btcentralplus.com (HELO pc6) ([86.162.135.195]) by c2beaomr07.btconnect.com with SMTP id GWY58498; Sat, 31 Mar 2012 12:27:41 +0100 (BST)
Message-ID: <006501cd0f28$bb177e80$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "George, Wes" <wesley.george@twcable.com>, <grow@ietf.org>, <v6ops@ietf.org>
References: <20120328112128.19122.59432.idtracker@ietfa.amsl.com> <DCC302FAA9FE5F4BBA4DCAD465693779173D6E9C51@PRVPEXVS03.corp.twcable.com>
Date: Sat, 31 Mar 2012 12:26:19 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4F76EA2D.0032, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2012.3.31.103620:17:7.944, ip=86.162.135.195, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __CP_URI_IN_BODY, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP
X-Junkmail-Status: score=10/50, host=c2beaomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020A.4F76EA2E.0024,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
Subject: Re: [GROW] draft-behringer-lla-only anddraft-ietf-grow-private-ip-sp-cores
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Mar 2012 11:27:50 -0000

----- Original Message -----
From: "George, Wes" <wesley.george@twcable.com>
To: <grow@ietf.org>; <v6ops@ietf.org>
Cc: <draft-behringer-lla-only@tools.ietf.org>
Sent: Saturday, March 31, 2012 1:14 AM
> Cross-posting to both lists again because I was unable to attend the v6ops
session where draft-behringer was discussed, draft-ietf-grow-private-ip-sp-cores
is likely nearing WGLC, and I believe that the issue I raised needs to be
addressed before either proceeds. I defer to the chairs of both groups to
determine how to manage this across the two groups.
>
> After reviewing both draft-grow-private-ip-sp-cores (Kirkham) and
draft-behringer-lla-only again, I am even more convinced that they either need
to be merged, or that draft-behringer needs to be abandoned altogether as a bad
idea. Draft-grow-private-ip-sp-cores is quite a lot more complete in its
discussion of the considerations around private IP usage, but focuses on IPv4,
meaning that it *is* incomplete for lack of discussion of IPv6, which is a
reality in most SP cores today. Nearly all of the same considerations apply for
IPv4 and IPv6 in this case, so there are probably a limited number of changes
that would be necessary to cover IPv6 in the Kirkham document.
<tp>
Disagree.  As you say, the grow draft is more or less complete, more or less
ready for WGLC.  And it has taken the IETF two years to get to this state.

IPv6 is different.  We probably know little as yet as to how it works or how it
should.

Adding IPv6 would put this work back a year or two, and given that GROW is not
the most lively of growps, it may never happen.

Get the grow draft out as an RFC while it is still of value to its audience.

Then contemplate a -bis with IPv6 if there is sufficient enthusiasm in a WG to
do so.

Tom Petch






> I think that we need to come to some consensus on the recommended behavior on
both cases. If the recommendation is different for one versus the other, we need
to have a unified and clear articulation as to why this is the case. It may be
that the consensus is to not recommend a behavior at all, and simply expand the
format of Kirkham's document to cover any IPv6-specific items, since it
discusses pros and cons evenly (as an informational doc) rather than
recommending anything as a BCP. My vote is to do this, as I am unconvinced that
use of LLA represents BCP today, nor should it. I outline some reasons below,
but that's probably not as critical if others agree that this is the proper
method to proceed with these documents.
>
>
>
> If draft-behringer is left as a separate document, here are some specific
comments:
> The advantages proposed in draft-behringer are IMO not enough to justify
recommending use of LLA.
> - Smaller routing tables can be achieved through other methods such as setting
the interfaces into passive mode in the IGP (so that they are not redistributed
into the IGP) and/or not redistributing connected routes. Further, as SPs make
great use of interface bundling (LAG), the number of interfaces with IP
addresses is dramatically reduced, making the need to pull the point to point
interfaces out of the routing table significantly lower.
> - Reduced attack surface - draft-ietf-grow-private-ip-sp-cores sections 10 and
11 discuss this in great detail, and come to the conclusion that it is of
limited benefit, and that alternatives exist to protect the infrastructure.
> - lower configuration complexity - while this is true, it is replaced by
additional complexity in troubleshooting. In the case of traces and pings
locally on the box, it adds the additional step of requiring the operator to use
extended ping and trace commands to specify the exit interface in order to make
the ping work (vs simply issuing "ping [ip address]"), and makes it nearly
impossible to derive the address of the remote interface without determining the
remote side router through some other means and logging into the router to look.
(vs practice today of using an IP in the same subnet, usually 1 digit up or down
that can be guessed to save time).
> - less address space: The other draft mentions this as well, in the context of
IPv4 where it might make a difference, but this simply is not much of a concern
with IPv6. An entire network could be numbered many times over out of one /64.
> -simpler DNS : Most ISPs operating at the scale where this makes any
difference at all have tools to build the DNS forward and reverse entries for
their infrastructure automatically based on the router name and interface name
extracted from their inventory tools. It's a few bits of scripting, so it's not
like having less interfaces in DNS results in any net reduction in work or
increase in the possibility of mistakes.
>
> - Draft-ietf-grow-private-ip-sp-cores rightly notes that the proposed solution
to broken pings/traces/PMTUD from draft-behringer (RFC 5837) has little or no
implementation. This makes it a hard sell as any sort of recommended solution
unless the benefits are much more significant than what is currently discussed
in draft-behringer. This has to be a large enough benefit to justify pushing
hard on router vendors to implement the feature and SPs to certify and deploy
the code, and frankly there are many more important features to consider.
>
> Thanks,
>
> Wes George
>
>
> > -----Original Message-----
> > From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
> > internet-drafts@ietf.org
> > Sent: Wednesday, March 28, 2012 7:21 AM
> > To: i-d-announce@ietf.org
> > Cc: grow@ietf.org
> > Subject: [GROW] I-D Action: draft-ietf-grow-private-ip-sp-cores-00.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories. This draft is a work item of the Global Routing Operations
> > Working Group of the IETF.
> >
> >       Title           : Issues with Private IP Addressing in the Internet
> >       Author(s)       : Anthony Kirkham
> >       Filename        : draft-ietf-grow-private-ip-sp-cores-00.txt
> >       Pages           : 15
> >       Date            : 2012-03-28
> >
> >    The purpose of this document is to provide a discussion of the
> >    potential problems of using private, RFC1918, or non-globally-
> >    routable addressing within the core of an SP network.  The discussion
> >    focuses on link addresses and to a small extent loopback addresses.
> >    While many of the issues are well recognised within the ISP
> >    community, there appears to be no document that collectively
> >    describes the issues.
> >
> >
> > A URL for this Internet-Draft is:
> >
http://www.ietf.org/internet-drafts/draft-ietf-grow-private-ip-sp-cores-00.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-grow-private-ip-sp-cores-00.txt
> >
> > _______________________________________________
> > GROW mailing list
> > GROW@ietf.org
> > https://www.ietf.org/mailman/listinfo/grow
>
> This E-mail and any of its attachments may contain Time Warner Cable
proprietary information, which is privileged, confidential, or subject to
copyright belonging to Time Warner Cable. This E-mail is intended solely for the
use of the individual or entity to which it is addressed. If you are not the
intended recipient of this E-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify the sender
immediately and permanently delete the original and any copy of this E-mail and
any printout.
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>
>

