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