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" <[email protected]> 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). > > 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 <[email protected]> > 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: [email protected] >> Subject: New Version Notification for draft-gersch-grow-revdns-bgp-00.txt >> Date: February 28, 2012 1:51:59 PM MST >> To: [email protected] >> Cc: [email protected], [email protected], [email protected] >> >> 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 >> [email protected] >> https://www.ietf.org/mailman/listinfo/grow >> > _______________________________________________ > GROW mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/grow _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
