Re: [IPsec] Mirja Kühlewind's Block on charter-ietf-ipsecme-10-00: (with BLOCK)

2016-09-01 Thread kathleen . moriarty . ietf
Sent from my iPhone > On Sep 1, 2016, at 5:35 AM, Mirja Kuehlewind (IETF) > wrote: > > Yes, that’s fine for me. I would say that providing guidance means that you > make one suggestion what to do but don’t specify a mandatory behavior. Ok, I'll update the text before

Re: [IPsec] Mirja Kühlewind's Block on charter-ietf-ipsecme-10-00: (with BLOCK)

2016-09-01 Thread Mirja Kuehlewind (IETF)
Yes, that’s fine for me. I would say that providing guidance means that you make one suggestion what to do but don’t specify a mandatory behavior. Mirja > Am 01.09.2016 um 05:13 schrieb Tommy Pauly : > > Hi Kathleen, > >> On Aug 31, 2016, at 6:53 PM, Kathleen Moriarty >>

Re: [IPsec] Mirja Kühlewind's Block on charter-ietf-ipsecme-10-00: (with BLOCK)

2016-08-31 Thread Tommy Pauly
Hi Kathleen, > On Aug 31, 2016, at 6:53 PM, Kathleen Moriarty > wrote: > > Tommy, > > On Wed, Aug 31, 2016 at 10:30 AM, Tommy Pauly > wrote: >> >>> On Aug 31, 2016, at 6:41 AM, Mirja Kuehlewind (IETF)

Re: [IPsec] Mirja Kühlewind's Block on charter-ietf-ipsecme-10-00: (with BLOCK)

2016-08-31 Thread Kathleen Moriarty
Tommy, On Wed, Aug 31, 2016 at 10:30 AM, Tommy Pauly wrote: > >> On Aug 31, 2016, at 6:41 AM, Mirja Kuehlewind (IETF) >> wrote: >> >> Hi all, >> >> thanks for providing the reference to the draft. That was very helpful and >> confirmed my initial

Re: [IPsec] Mirja Kühlewind's Block on charter-ietf-ipsecme-10-00: (with BLOCK)

2016-08-31 Thread Tommy Pauly
> On Aug 31, 2016, at 6:41 AM, Mirja Kuehlewind (IETF) > wrote: > > Hi all, > > thanks for providing the reference to the draft. That was very helpful and > confirmed my initial assumption that you don’t want to ‚change‘ TCP. So this > work seems to be fine in this

Re: [IPsec] Mirja Kühlewind's Block on charter-ietf-ipsecme-10-00: (with BLOCK)

2016-08-31 Thread Mirja Kuehlewind (IETF)
Hi Tommy, thanks for the info. I understand the need for using TCP and also the need for standardization here. It was just not clear to me what exactly need to be done because I didn’t have the reference to the draft. You as you said below what you need is guidance on "how to encapsulate IKE

Re: [IPsec] Mirja Kühlewind's Block on charter-ietf-ipsecme-10-00: (with BLOCK)

2016-08-31 Thread Paul Wouters
On Wed, 31 Aug 2016, Mirja Kuehlewind (IETF) wrote: thanks for providing the reference to the draft. That was very helpful and confirmed my initial assumption that you don’t want to ‚change‘ TCP. So this work seems to be fine in this group, however, the wording in the charter is very

Re: [IPsec] Mirja Kühlewind's Block on charter-ietf-ipsecme-10-00: (with BLOCK)

2016-08-31 Thread Tero Kivinen
Mirja Kuehlewind (IETF) writes: > thanks for providing the reference to the draft. That was very > helpful and confirmed my initial assumption that you don’t want to > ‚change‘ TCP. So this work seems to be fine in this group, however, > the wording in the charter is very misleading. What's about

Re: [IPsec] Mirja Kühlewind's Block on charter-ietf-ipsecme-10-00: (with BLOCK)

2016-08-31 Thread Mirja Kuehlewind (IETF)
Hi all, thanks for providing the reference to the draft. That was very helpful and confirmed my initial assumption that you don’t want to ‚change‘ TCP. So this work seems to be fine in this group, however, the wording in the charter is very misleading. What's about the following? "There have

Re: [IPsec] Mirja Kühlewind's Block on charter-ietf-ipsecme-10-00: (with BLOCK)

2016-08-31 Thread Yoav Nir
> On 31 Aug 2016, at 3:21 PM, Tero Kivinen wrote: > > Mirja Kuehlewind (IETF) writes: >> thanks for the reply. Very helpful background info. Maybe even put >> more information in the charter text. > > I think it belongs to the actual draft, not to the charter, perhaps we >

Re: [IPsec] Mirja Kühlewind's Block on charter-ietf-ipsecme-10-00: (with BLOCK)

2016-08-31 Thread Paul Wouters
On Wed, 31 Aug 2016, Tero Kivinen wrote: Based on Tero's mail I understand how the stack looks like but that's not clear from the text because there is not really anything like a TCP tunnel. So the big question is, based on the stack indicated by Tero, do you have two full TCP connections

Re: [IPsec] Mirja Kühlewind's Block on charter-ietf-ipsecme-10-00: (with BLOCK)

2016-08-31 Thread Tero Kivinen
Mirja Kuehlewind (IETF) writes: > thanks for the reply. Very helpful background info. Maybe even put > more information in the charter text. I think it belongs to the actual draft, not to the charter, perhaps we should put the draft-ietf-ipsecme-tcp-encaps in the charter, as a working draft. >

Re: [IPsec] Mirja Kühlewind's Block on charter-ietf-ipsecme-10-00: (with BLOCK)

2016-08-31 Thread Mirja Kuehlewind (IETF)
Hi Tero, thanks for the reply. Very helpful background info. Maybe even put more information in the charter text. When you say "the 3gpp specification did not consider or specify all needed things for the protocol“, can you be more specific here? I’m not saying that this is the wrong working