[netext] #8: TSV review of LR PS I-D

"netext issue tracker" <trac+netext@trac.tools.ietf.org> Mon, 21 March 2011 16:04 UTC

Return-Path: <trac+netext@trac.tools.ietf.org>
X-Original-To: netext@core3.amsl.com
Delivered-To: netext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C914A3A6886 for <netext@core3.amsl.com>; Mon, 21 Mar 2011 09:04:20 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jPTyMWrM3okm for <netext@core3.amsl.com>; Mon, 21 Mar 2011 09:04:19 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id EB84A3A6881 for <netext@ietf.org>; Mon, 21 Mar 2011 09:04:19 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.74) (envelope-from <trac+netext@trac.tools.ietf.org>) id 1Q1hbw-0000Z9-Tp; Mon, 21 Mar 2011 09:05:40 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: netext issue tracker <trac+netext@trac.tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: liebsch@neclab.eu, basavaraj.patil@nokia.com
X-Trac-Project: netext
Date: Mon, 21 Mar 2011 16:05:40 -0000
X-URL: http://tools.ietf.org/netext/
X-Trac-Ticket-URL: https://svn.tools.ietf.org/wg/netext/trac/ticket/8
Message-ID: <066.ac042b61a410c326c291fd90be684bb3@trac.tools.ietf.org>
X-Trac-Ticket-ID: 8
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: liebsch@neclab.eu, basavaraj.patil@nokia.com, draft-ietf-netext-pmip6-lr-ps@tools.ietf.org, netext@ietf.org
X-SA-Exim-Mail-From: trac+netext@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: netext@ietf.org, draft-ietf-netext-pmip6-lr-ps@tools.ietf.org
Subject: [netext] #8: TSV review of LR PS I-D
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/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: Mon, 21 Mar 2011 16:04:20 -0000

#8: TSV review of LR PS I-D

 Hello,
 I've reviewed this document as part of the transport area
 directorate's ongoing effort to review key IETF documents. These
 comments were written primarily for the transport area directors, but
 are copied to the document's authors for their information and to
 allow them to address any issues raised. The authors should consider
 this review together with any other last-call comments they
 receive. Please always CC tsv-dir@ietf.org if you reply to or forward
 this review.

 Summary:

 This draft describes the problem space for localized routing in PMIPv6,
 which supports direct communication between MAGs for MN and CN.
 This draft is basically ready for publication and I couldn't
 find any transport related issues in the draft.

 Minor comments:

 Would it be better to mention error detection and fallback function in
 Functional Requirements? It would be useful and helpful to fall back
 to normal routing when something happens.

 I believe localize routing is very useful in most cases. However, I think
 there will be the cases where we had better avoid localized routing,
 such as a case where there are some restrictions (policy, network quality
 or configuration, etc) in communications between MAGs.
 It might be better to address having some kind of control to enable
 localized routing in Functional Requirements in addition to checking
 source and destination addresses.

 Thanks,
 --
 Yoshifumi Nishida

-- 
---------------------------------------+------------------------------------
 Reporter:  basavaraj.patil@…          |       Owner:  liebsch@…        
     Type:  defect                     |      Status:  new              
 Priority:  minor                      |   Milestone:                   
Component:  pmip6-lr-ps                |     Version:                   
 Severity:  -                          |    Keywords:                   
---------------------------------------+------------------------------------

Ticket URL: <https://svn.tools.ietf.org/wg/netext/trac/ticket/8>
netext <http://tools.ietf.org/netext/>