From lha at it.su.se  Thu Jul 13 09:34:04 2006
From: lha at it.su.se (=?ISO-8859-1?Q?Love_H=F6rnquist_=C5strand?=)
Date: Thu, 13 Jul 2006 18:34:04 +0200
Subject: [anonsec] ietf66 btns minutes
Message-ID: <EAE7F0A5-1FD3-4B91-9528-8BD174D68234@it.su.se>

Hello,

I just published the minutes for the meeting on the meeting materials  
website.
I've included the parts for that needs to be confirmed on the mailing  
list
and action item below.

http://www3.ietf.org/proceedings/06jul/minutes/btns.txt

Love


* Decisions made

	- Two document for the API documents
	  One for SPD manipulation and one for channel bindings.

* Action items

	- AS/PS document submitted by August.

	- Steve Kent should send PAD/SPD examples to Nicolas and
	  Michael for BTNS-core document.

	- btns-core: fix inconsistency issues and update the tables to
	  describe missing fields.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://mailman.postel.org/pipermail/anonsec/attachments/20060713/455fa254/PGP.bin

From lha at it.su.se  Thu Jul 13 09:54:46 2006
From: lha at it.su.se (=?ISO-8859-1?Q?Love_H=F6rnquist_=C5strand?=)
Date: Thu, 13 Jul 2006 18:54:46 +0200
Subject: [anonsec] btns - ietf66
Message-ID: <55A9ED29-BA9C-41BE-B52E-3D5FDADE8C5D@it.su.se>


BTNS meet on Tuesday on IETF66. We discussed the problem and
applicability statement document. It should be done for WG-LC in
August.  One of the issues that came up is how to deal with
credential caching and leap of faith (and to define that mean) and
how much that that is in scope for BTNS.

The core document describing BTNS have progress nicely and there are
very few outstanding issues on the document.

We have started to look at the API problem that the WG is charted to
work on. There will probably be two documents describing the API, one
for channel bindings and one for SPD/PAD manipulation. We had a
decision if there was any overlap with the work from SHIM6 and HIP,
but the WG thought there was none and that we didn't need to
coordinate our efforts.

Love


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://mailman.postel.org/pipermail/anonsec/attachments/20060713/de0b7f6d/PGP.bin

From miika at iki.fi  Thu Jul 13 10:06:06 2006
From: miika at iki.fi (Miika Komu)
Date: Thu, 13 Jul 2006 20:06:06 +0300 (EEST)
Subject: [anonsec] btns - ietf66
In-Reply-To: <55A9ED29-BA9C-41BE-B52E-3D5FDADE8C5D@it.su.se>
References: <55A9ED29-BA9C-41BE-B52E-3D5FDADE8C5D@it.su.se>
Message-ID: <Pine.SOL.4.64.0607132004160.19778@kekkonen.cs.hut.fi>

On Thu, 13 Jul 2006, Love H?rnquist ?strand wrote:

> We have started to look at the API problem that the WG is charted to
> work on. There will probably be two documents describing the API, one
> for channel bindings and one for SPD/PAD manipulation. We had a
> decision if there was any overlap with the work from SHIM6 and HIP,
> but the WG thought there was none and that we didn't need to
> coordinate our efforts.

I thought that the decision was that there is no overlap with SHIM6 and 
BTNS? At least we have been discussing with Michael that we could have 
some shared APIs with HIP and BTNS.

-- 
Miika Komu                                       http://www.iki.fi/miika/

From lha at it.su.se  Thu Jul 13 10:31:14 2006
From: lha at it.su.se (=?ISO-8859-1?Q?Love_H=F6rnquist_=C5strand?=)
Date: Thu, 13 Jul 2006 19:31:14 +0200
Subject: [anonsec] btns - ietf66
In-Reply-To: <Pine.SOL.4.64.0607132004160.19778@kekkonen.cs.hut.fi>
References: <55A9ED29-BA9C-41BE-B52E-3D5FDADE8C5D@it.su.se>
	<Pine.SOL.4.64.0607132004160.19778@kekkonen.cs.hut.fi>
Message-ID: <0EE60D29-C864-439C-9701-240183D9A99B@it.su.se>


13 jul 2006 kl. 19.06 skrev Miika Komu:

> On Thu, 13 Jul 2006, Love H?rnquist ?strand wrote:
>
>> We have started to look at the API problem that the WG is charted to
>> work on. There will probably be two documents describing the API, one
>> for channel bindings and one for SPD/PAD manipulation. We had a
>> decision if there was any overlap with the work from SHIM6 and HIP,
>> but the WG thought there was none and that we didn't need to
>> coordinate our efforts.
>
> I thought that the decision was that there is no overlap with SHIM6  
> and BTNS? At least we have been discussing with Michael that we  
> could have some shared APIs with HIP and BTNS.

My note is clearly wrong, I mis-understod what Micheal told us.

There is overlap with HIP. Micheal and you seem to have this already  
ironed out
how to deal with it.

Love


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://mailman.postel.org/pipermail/anonsec/attachments/20060713/24219465/PGP.bin

From hartmans-ietf at mit.edu  Mon Jul 31 06:11:57 2006
From: hartmans-ietf at mit.edu (Sam Hartman)
Date: Mon, 31 Jul 2006 09:11:57 -0400
Subject: [anonsec] [saag] IPsec configuration via BGP--softwires to
	support overlay network confidentiality/integrity
In-Reply-To: <44B2D50C.5020508@cisco.com> (Mark Townsley's message of "Mon, 10
	Jul 2006 18:30:36 -0400")
References: <tslslo58eum.fsf@cz.mit.edu> <44B2D50C.5020508@cisco.com>
Message-ID: <tslirldc40y.fsf@cz.mit.edu>

>>>>> "Mark" == Mark Townsley <townsley at cisco.com> writes:

    Mark> Sam, was there any response to this?


Yes.  The responses were all positive.

