List Info

Thread: I-D Action:draft-ietf-btns-connection-latching-02.txt




I-D Action:draft-ietf-btns-connection-latchi ng-02.txt
user name
2007-09-12 01:50:01
A New Internet-Draft is available from the on-line
Internet-Drafts directories.
This draft is a work item of the Better-Than-Nothing
Security Working Group of the IETF.


	Title           : IPsec Channels: Connection Latching
	Author(s)       : N. Williams
	Filename        :
draft-ietf-btns-connection-latching-02.txt
	Pages           : 18
	Date            : 2007-09-12

This document specifies, abstractly, how to interface
applications
and transport protocols with IPsec so as to create
"channels" by
"latching" "connections" (packet flows)
to certain IPsec Security
Association (SA) parameters for the lifetime of the
connections.
This can be used to protect applications against
accidentally
exposing live packet flows to unintended peers, whether as
the result
of a reconfiguration of IPsec or as the result of using weak
peer
identity to peer address associations.

Weak association of peer ID and peer addresses is at the
core of
Better Than Nothing Security (BTNS), thus connection
latching can add
a significant measure of protection to BTNS IPsec nodes.  A
model of
of connection latching based on a modification to the child
SA
authorization process is given.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-draft
s/draft-ietf-btns-connection-latching-02.txt

To remove yourself from the I-D Announcement list, send a
message to
i-d-announce-requestietf.org with the word unsubscribe in the
body of 
the message.
You can also visit h
ttps://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login
with the 
username "anonymous" and a password of your e-mail
address. After 
logging in, type "cd internet-drafts" and then
	"get
draft-ietf-btns-connection-latching-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/s
hadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailservietf.org.
In the body type:
	"FILE
/internet-drafts/draft-ietf-btns-connection-latching-02.txt&
quot;.

NOTE:   The mail server at ietf.org can return the document
in
	MIME-encoded form by using the "mpack" utility. 
To use this
	feature, insert the command "ENCODING mime"
before the "FILE"
	command.  To decode the response(s), you will need
"munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant
mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which
have been split
	up into multiple messages), so check your local
documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail
reader
implementation to automatically retrieve the ASCII version
of the
Internet-Draft.

_______________________________________________

  
  
Re: I-D Action:draft-ietf-btns-connection-latchi ng-02.txt
user name
2007-09-17 15:24:52
On Fri, Sep 14, 2007 at 12:41:33PM -0500, Nicolas Williams
wrote:
> I'd appreciate some feedback on this version of the
connection latching
> I-D.
> 
>  - In particular I'm looking for feedback on section
2.1, whether the
>    proposed modification to the child SA authorization
process is
>    reasonable.  (Note: the child SA authorization
process is modified
>    only when connection latching is used; see also the
note in section
>    2.3 about a PAD entry flag to preserve traditional
semantics.)

I've found a way around that.  I've submitted -03 just now.

>  - Neither section 2.1 nor 2.2 talks about when to
initiate SAs.  But it
>    should be obvious that the right time is when a
latch is initiated.

Fixed.

>  - Section 3 doesn't say much about the SPD.
> 
>    In particular, when an application requests that
traffic be PROTECTED
>    that would otherwise have been BYPASSed (or when a
locally privileged
>    app requests the opposite) then the SPD should be
temporarily
>    modified accordingly.  This should be described in
detail.

Sections 2.1 and 3 now both deal with this properly,
methinks.

Comments welcome.
_______________________________________________

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )