Re: [IPsec] Rekeying of child sa, Question on TS handling according to RFC 5996
Yoav Nir <ynir.ietf@gmail.com> Thu, 21 August 2014 19:21 UTC
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 655191A89F5 for <ipsec@ietfa.amsl.com>; Thu, 21 Aug 2014 12:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KbXhiKfNrIwg for <ipsec@ietfa.amsl.com>; Thu, 21 Aug 2014 12:21:12 -0700 (PDT)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66D071A86DF for <ipsec@ietf.org>; Thu, 21 Aug 2014 12:21:12 -0700 (PDT)
Received: by mail-we0-f169.google.com with SMTP id u56so9815101wes.0 for <ipsec@ietf.org>; Thu, 21 Aug 2014 12:21:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2luDZiG4+wN6a5RAxA2hk+boLDQnBM+3nr9qeIdmawc=; b=BiYHuWISDWQ94GiLdXbxkDdD5w72b9MqdfOjCziUGMuq8+8/nwQkmWMBcs4Wod17Og qKr78xIyuY7cLcgQeDeg3mUOUXq4gjifLyWcXxNJ2Fhr5mCwX0Lt02ChQ7gtjyBDEELn +sDSfJx8k2U3iyRjcM1YS83VuW7f253BrsB8a/BmlFRU6lqnVG8rZ6napnjQjKtBMYeu e5coqVUkxgepyXz6ciwMP7BH3YE9/9E1olHX3zT37TJ2/ATWJFFxjZEnfHJl1QkFMiwN b35l+FFdjel76qR0mWlnWuvG3dl/chgg7YKo1iy8/LHcAv5zUrk60g/yKAN87xadfFoy l33A==
X-Received: by 10.180.205.234 with SMTP id lj10mr273184wic.1.1408648870793; Thu, 21 Aug 2014 12:21:10 -0700 (PDT)
Received: from [192.168.1.104] (bzq-84-109-50-18.red.bezeqint.net. [84.109.50.18]) by mx.google.com with ESMTPSA id vn10sm68885101wjc.28.2014.08.21.12.21.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Aug 2014 12:21:10 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: text/plain; charset="us-ascii"
From: Yoav Nir <ynir.ietf@gmail.com>
X-Priority: 3
In-Reply-To: <257268920DEA479E9FC65BFA164783C2@buildpc>
Date: Thu, 21 Aug 2014 22:21:07 +0300
Content-Transfer-Encoding: 7bit
Message-Id: <66302A57-27E5-46EF-A373-A82008169B8E@gmail.com>
References: <F68C660364DABE41AF4617F517EF548411707BE2@ESESSMB309.ericsson.se> <21493.55390.157248.181030@fireball.kivinen.iki.fi> <257268920DEA479E9FC65BFA164783C2@buildpc>
To: Valery Smyslov <svanru@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipsec/S5UcdKlN3iMfgi4T515bmDodXI4
Cc: ipsec@ietf.org, sec-ads@tools.ietf.org, Tero Kivinen <kivinen@iki.fi>, Pål Dammvik <pal.dammvik@ericsson.com>
Subject: Re: [IPsec] Rekeying of child sa, Question on TS handling according to RFC 5996
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Aug 2014 19:21:14 -0000
+1 On Aug 21, 2014, at 2:49 PM, Valery Smyslov <svanru@gmail.com> wrote: > Hi Tero, > >> This is also question what should we do for the rfc5996bis. >> We have two options, we removed the text saying section 2.9.2 was >> added in the RFC5996, or we add the section 2.9.2 from the ticket #12, >> and add note that saying that this time we really added it... >> What does the working group feel we should do? Note, that if we add >> the 2.9.2 that might cause delays, as I am not sure if we can do that >> kind of change after IESG has already approved the rfc5996bis (it is >> now in the AUTH48), meaning it might need IESG to recheck that part. >> On the other hand I think adding the text which we already have >> approved in 2009 to the specification would be the right thing to do, >> as there clearly is need for clarification (as we can see from the >> Dammvik's question). > > I think we should add this text. The text is useful and I don't see > a reason to sacrifice it in favour to speed up RFC publication. > > Regards, > Valery. > >> kivinen@iki.fi > > _______________________________________________ > IPsec mailing list > IPsec@ietf.org > https://www.ietf.org/mailman/listinfo/ipsec
- [IPsec] Rekeying of child sa, Question on TS hand… Pål Dammvik
- [IPsec] Rekeying of child sa, Question on TS hand… Tero Kivinen
- Re: [IPsec] Rekeying of child sa, Question on TS … Valery Smyslov
- Re: [IPsec] Rekeying of child sa, Question on TS … Pål Dammvik
- Re: [IPsec] Rekeying of child sa, Question on TS … Yoav Nir
- Re: [IPsec] Rekeying of child sa, Question on TS … Kathleen Moriarty
- [IPsec] Typos in draft-kivinen-ipsecme-ikev2-rfc5… Valery Smyslov
- [IPsec] Typos in draft-kivinen-ipsecme-ikev2-rfc5… Tero Kivinen
- Re: [IPsec] Typos in draft-kivinen-ipsecme-ikev2-… Valery Smyslov
- Re: [IPsec] Typos in draft-kivinen-ipsecme-ikev2-… Valery Smyslov
- Re: [IPsec] Typos in draft-kivinen-ipsecme-ikev2-… Valery Smyslov
- Re: [IPsec] Typos in draft-kivinen-ipsecme-ikev2-… Paul Wouters
- Re: [IPsec] Typos in draft-kivinen-ipsecme-ikev2-… Valery Smyslov
- Re: [IPsec] Typos in draft-kivinen-ipsecme-ikev2-… Paul Wouters
- [IPsec] More nits in draft-kivinen-ipsecme-ikev2-… Valery Smyslov
- Re: [IPsec] Typos in draft-kivinen-ipsecme-ikev2-… Tero Kivinen
- Re: [IPsec] Typos in draft-kivinen-ipsecme-ikev2-… Tero Kivinen
- [IPsec] More nits in draft-kivinen-ipsecme-ikev2-… Tero Kivinen