Hi,

As a co-author of the draft I am of course supporting the draft and will
contribute to it.

BR,
Daniel

On Tue, Dec 2, 2014 at 10:20 PM, Yaron Sheffer <yaronf.i...@gmail.com>
wrote:

> And similarly for this draft: please speak up if you're interested in this
> document and are willing to contribute as co-author or reviewer.
>
> Thanks,
>         Yaron
>
>
> On 11/25/2014 10:06 PM, Paul Hoffman wrote:
>
>> <chair hats on>
>>
>> Greetings again. The "Clone IKE SA" proposal tries to optimize IKE SA
>> setup in cases where VPN gateways have multiple interfaces and want to
>> establish different SAs on the different interfaces without having to
>> repeat the IKE authentication. Instead, they could clone a single IKE SA
>> multiple times, and then move it to different interfaces using MOBIKE.
>>
>> If you agree with the need to standardize this usage, and believe that
>> draft-mglt-ipsecme-clone-ike-sa is likely to be a good starting place
>> for that standardization, and are willing to review and contribute text to
>> the document if it is adopted by the WG, please say so on the list. This WG
>> has a history of adopting documents but then not having enough reviewers
>> for us to feel confident that we are making a good standard, so we need to
>> see a reasonable number of actively interested people before we adopt the
>> document. If it is not adopted, the authors can ask for it to be published
>> as an RFC through individual submission or by the Independent Submissions
>> Editor.
>>
>> Please reply by December 8, 2015.
>>
>> --Paul Hoffman and Yaron Sheffer
>> _______________________________________________
>> IPsec mailing list
>> IPsec@ietf.org
>> https://www.ietf.org/mailman/listinfo/ipsec
>>
>>
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec
>



-- 
Daniel Migault
Orange Labs -- Security
+33 6 70 72 69 58
_______________________________________________
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec

Reply via email to