Hi,

we've done a lot of work on this document as a group, and it may well be
ready to go through WG Last Call. However it did go through 4 revisions
since San Francisco. So before we proceed, I'd like to ask if anybody is
seeing showstopper issues with the draft in its current form. In which case
we'll need to work on this draft some more before sending it to LC. If there
are small issues though, we can defer them to the last call process.

Please respond to the list, or to Paul and myself.

Thanks,
        Yaron

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of
> [email protected]
> Sent: Wednesday, June 24, 2009 18:45
> To: [email protected]
> Cc: [email protected]
> Subject: [IPsec] I-D Action:draft-ietf-ipsecme-traffic-visibility-05.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the IP Security Maintenance and Extensions
> Working Group of the IETF.
> 
> 
>       Title           : Wrapped ESP for Traffic Visibility
>       Author(s)       : K. Grewal, et al.
>       Filename        : draft-ietf-ipsecme-traffic-visibility-05.txt
>       Pages           : 13
>       Date            : 2009-06-24
> 
> This document describes the Wrapped Encapsulating Security
> Payload (WESP) protocol, which builds on top of Encapsulating
> Security Payload (ESP) [RFC4303] and is designed to allow
> intermediate devices to ascertain if ESP-NULL [RFC2410] is being
> employed and hence inspect the IPsec packets for network
> monitoring and access control functions.  Currently in the IPsec
> standard, there is no way to differentiate between ESP
> encryption and ESP NULL encryption by simply examining a packet.
> This poses certain challenges to the intermediate devices that
> need to deep inspect the packet before making a decision on what
> should be done with that packet (Inspect and/or Allow/Drop). The
> mechanism described in this document can be used to easily
> disambiguate ESP-NULL from ESP encrypted packets, without
> compromising on the security provided by ESP.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-ipsecme-traffic-visibility-
> 05.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.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

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

Reply via email to