[netext] Stephen Farrell's Discuss on draft-ietf-netext-update-notifications-08: (with DISCUSS and COMMENT)

"Stephen Farrell" <stephen.farrell@cs.tcd.ie> Tue, 24 September 2013 10:38 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65F8621F9D19; Tue, 24 Sep 2013 03:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4HnxNsmov8YD; Tue, 24 Sep 2013 03:38:21 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6263C11E80DE; Tue, 24 Sep 2013 03:38:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.72
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20130924103819.29616.21400.idtracker@ietfa.amsl.com>
Date: Tue, 24 Sep 2013 03:38:19 -0700
Cc: netext@ietf.org, draft-ietf-netext-update-notifications@tools.ietf.org, netext-chairs@tools.ietf.org
Subject: [netext] Stephen Farrell's Discuss on draft-ietf-netext-update-notifications-08: (with DISCUSS and COMMENT)
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Sep 2013 10:38:21 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-netext-update-notifications-08: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-netext-update-notifications/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------


5.2: What happens if the IPsec SA is re-negotiated
automatically? Isn't there a potential layering/sync problem
so that these notifications couldn't ever be verified since a
new SA would be in use? I think you just need to say the same
or an automatically renegotiated SA (not sure what's the
right terminology, sorry). I think 6.1 has the same issue and
maybe other bits too. That kind of check also seems to
imply that the interface between the MAG or LMA and the
IPsec code needs to know that the right SA is being used
which could be tricky. What's really done here?


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


- 4.1: What does "ANI-PARAMS-REQUESTED" mean? Probably all
these reasons need an explanation and/or (forward) reference.