[netext] draft-ietf-netext-pmipv6-flowmob-08

Behcet Sarikaya <sarikaya2012@gmail.com> Thu, 13 February 2014 17:25 UTC

Return-Path: <sarikaya2012@gmail.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7550B1A0325 for <netext@ietfa.amsl.com>; Thu, 13 Feb 2014 09:25:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 hw7Hb8z1gUeQ for <netext@ietfa.amsl.com>; Thu, 13 Feb 2014 09:25:08 -0800 (PST)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) by ietfa.amsl.com (Postfix) with ESMTP id 4C7A51A0323 for <netext@ietf.org>; Thu, 13 Feb 2014 09:25:07 -0800 (PST)
Received: by mail-lb0-f176.google.com with SMTP id w7so8340895lbi.21 for <netext@ietf.org>; Thu, 13 Feb 2014 09:25:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=50pMZqMyjlZgUxUKtocFdoIr0QmYVPX6faWzjJZMSus=; b=Fsb2ikYfa5zw6jnTBGFzBqELryXB0CjBJUWz5YFjJccYF7ffRvqGKnBXiz7NVrTARX NmnCNlfcdw1uPo1KljgN0mv4O0CN9npQVjz9inq++8QrPS3tSBQXcYk5Z/Iiip8mKYvO TM1/PFoSVJ0c4sFgZPRYb5+HefgBudecqmZhCGGEEMatdSlWEJ8ETG+L7QIdlmz1SdJe AaYo3xKO/Dy87w5YUBa/6r9u3ZMWBJS+yDB9UlbzqrTcBl4s0bnLtSJ6NakV5427u18Q 3Td0In6vawSfB4YSO9dK8xHN87sH+x/MV8e+wOH8PtIiscNotYDdJollrVAC3Ivyj4Rr HTZw==
MIME-Version: 1.0
X-Received: by 10.112.134.38 with SMTP id ph6mr1789859lbb.16.1392312305421; Thu, 13 Feb 2014 09:25:05 -0800 (PST)
Received: by 10.114.170.193 with HTTP; Thu, 13 Feb 2014 09:25:05 -0800 (PST)
Date: Thu, 13 Feb 2014 11:25:05 -0600
Message-ID: <CAC8QAccTVgFqKmJJwpR334k+dq=cAPvF=59zQztBrNSQN0mABA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "netext@ietf.org" <netext@ietf.org>
Content-Type: multipart/alternative; boundary="047d7b3a894661905d04f24cf8f8"
Subject: [netext] draft-ietf-netext-pmipv6-flowmob-08
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
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: Thu, 13 Feb 2014 17:25:09 -0000

Hi all,

I was reading this document once more and this point somehow sticks so I
thought I should share with the WG:

Section 3.2.1 presents a solution with LMA assigning the same prefix to
different interfaces of MN.

So the draft can easily say that this is the solution to flow mobility in
PMIP, PMIP is extended to adopt this prefix-assignment policy and here is
the solution.

Why continue and present another solution in Section 3.2.2?

Another comment on Section 3.1.
Why are these three the only use cases?
I served in the editorial team initially and the main use cases were
MAG-initiated flow mobility and LMA-initiated flow mobility and actually
there were many solution drafts proposing solution for each and those
drafts were taken as input by the editorial team.

What happened to that in Section 3.1?

Regards,

Behcet