Re: [RPSEC] BGP Security Requirements v08

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>> I think so.... I wonder how this overlaps with the p-2-p bgp draft also
>> being considered?
> 
> I don't quite know what you mean by a p-2-p bgp draft.  The behringer
> draft concerns the security requirements of protecting the bgp peer to
> bgp peer connection (e.g., TCP MD5).  Perhaps that is what you are
> talking about?
> 
> http://www.ietf.org/internet-drafts/draft-behringer-bgp-session-sec-req-01.txt
> 
> Abstract
> 
>    The document "BGP security requirements"
>    (draft-ietf-rpsec-bgpsecrec-07) specifies general security
>    requirements for BGP.  However, specific security requirements for
>    single BGP sessions, i.e., the connection between two BGP peers, are
>    only touched on briefly in the section "transport layer protection".
>    This document expands on this particular aspect of BGP security,
>    defining the security requirements between two BGP peers.

Yes... We should pick this work up as a WG item, I think, because it
really relates directly to the charter. But, I'll leave it to Tony to
bring it up at the Chicago meeting (it overlaps with Networkers this
time, and I really can't skip Networkers, *sigh*.

We should try and see what folks think on list before then, if possible,
though, I think (?).

:-)

Russ

- --
riw@cisco.com CCIE <>< Grace Alone

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGl/UxER27sUhU9OQRAhb4AKDJRU5Emu0HvOTK4IZ1qxQoAk62DgCeKP1P
vlNLckQ+M00dNx/MrSsDboo=
=/PTq
-----END PGP SIGNATURE-----

_______________________________________________
RPSEC mailing list
RPSEC@ietf.org
https://www1.ietf.org/mailman/listinfo/rpsec