Re: [IPsec] Issue #90: Shorter WESP negotiation

2009-05-04 Thread Grewal, Ken
9 4:49 AM >To: Grewal, Ken >Cc: ipsec@ietf.org >Subject: [IPsec] Issue #90: Shorter WESP negotiation > >Grewal, Ken writes: >> In the current traffic visibility draft, we indicate that WESP can be >> negotiated via IKEv2 using a new protocol identifier. >> Charlie

[IPsec] Issue #90: Shorter WESP negotiation

2009-05-04 Thread Tero Kivinen
Grewal, Ken writes: > In the current traffic visibility draft, we indicate that WESP can be > negotiated via IKEv2 using a new protocol identifier. > Charlie Kaufman suggested that it may be plausible to use a notification > method along the lines of USE_TRANSPORT_MODE in RFC 4306, where the type

Re: [IPsec] Issue #90: Shorter WESP negotiation

2009-05-02 Thread Grewal, Ken
om: ipsec-boun...@ietf.org [mailto:ipsec-boun...@ietf.org] On Behalf Of >Yoav Nir >Sent: Saturday, May 02, 2009 2:41 PM >To: Grewal, Ken; ipsec@ietf.org >Subject: Re: [IPsec] Issue #90: Shorter WESP negotiation > >Grewal, Ken wrote: >> >> Issue #90: shorter WESP negotiation &g

Re: [IPsec] Issue #90: Shorter WESP negotiation

2009-05-02 Thread Yoav Nir
Grewal, Ken wrote: > > Issue #90: shorter WESP negotiation > > In the current traffic visibility draft, we indicate that WESP can be > negotiated via IKEv2 using a new protocol identifier. > Charlie Kaufman suggested that it may be plausible to use a notification > method along the lines of USE_TR

[IPsec] Issue #90: Shorter WESP negotiation

2009-04-30 Thread Grewal, Ken
All, As we prepare to submit the next revision of the WESP draft, we wanted to get some discussion / feedback on some open ticket items. Issue #90: shorter WESP negotiation In the current traffic visibility draft, we indicate that WESP can be negotiated via IKEv2 using a new protocol identifier.