Belatedly looking at this, I believe that the SSH subsystem name should be
registered with IANA.

Also, my experience of the IESG is that they will want more by way of security
considerations.

The recent draft-ietf-netconf-rfc4742bis gives exemplars of what I have in mind.

Tom Petch


----- Original Message -----
From: <[email protected]>
To: <[email protected]>
Cc: <[email protected]>
Sent: Tuesday, February 15, 2011 10:15 PM
Subject: [sidr] I-D Action:draft-ietf-sidr-rpki-rtr-08.txt


> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> This draft is a work item of the Secure Inter-Domain Routing Working Group of
the IETF.
>
>
> Title           : The RPKI/Router Protocol
> Author(s)       : R. Bush, R. Austein
> Filename        : draft-ietf-sidr-rpki-rtr-08.txt
> Pages           : 21
> Date            : 2011-02-15
>
> In order to formally validate the origin ASes of BGP announcements,
> routers need a simple but reliable mechanism to receive RPKI
> [I-D.ietf-sidr-arch] or analogous prefix origin data from a trusted
> cache.  This document describes a protocol to deliver validated
> prefix origin data to routers over ssh.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-sidr-rpki-rtr-08.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>


--------------------------------------------------------------------------------


> _______________________________________________
> sidr mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/sidr
>

_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to