Re: [shim6] Working Group Last Call draft-ietf-shim6-applicability

Alberto García <alberto@it.uc3m.es> Wed, 06 October 2010 09:55 UTC

Return-Path: <alberto@it.uc3m.es>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61BB53A6EE1 for <shim6@core3.amsl.com>; Wed, 6 Oct 2010 02:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.631
X-Spam-Level:
X-Spam-Status: No, score=-4.631 tagged_above=-999 required=5 tests=[AWL=-0.632, BAYES_00=-2.599, MANGLED_TOOL=2.3, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 dbx8sYcfY+hd for <shim6@core3.amsl.com>; Wed, 6 Oct 2010 02:55:15 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132]) by core3.amsl.com (Postfix) with ESMTP id C7F0C3A6B2A for <shim6@ietf.org>; Wed, 6 Oct 2010 02:55:14 -0700 (PDT)
X-uc3m-safe: yes
Received: from bombo (bombo.it.uc3m.es [163.117.139.125]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by smtp02.uc3m.es (Postfix) with ESMTP id 64A2A704071; Wed, 6 Oct 2010 11:56:11 +0200 (CEST)
From: =?iso-8859-15?Q?Alberto_Garc=EDa?= <alberto@it.uc3m.es>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>, "'Geoff Huston'" <gih@apnic.net>
References: <AF53E127-EBA8-4B65-ACFD-B9B5A0071B8A@apnic.net> <4CAA687F.7090002@gmail.com>
Date: Wed, 6 Oct 2010 11:56:10 +0200
Message-ID: <BCE37A03CFFC45B786DA22DA29A3A008@bombo>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <4CAA687F.7090002@gmail.com>
Thread-Index: ActkHx1jtdCjAgMEQxi4Ev8Sk0SmPgBEEpCQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-6.0.0.1038-17686.006
Cc: shim6-chairs@tools.ietf.org, draft-ietf-shim6-applicability@tools.ietf.org, 'shim6' <shim6@ietf.org>
Subject: Re: [shim6] Working Group Last Call draft-ietf-shim6-applicability
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 09:55:16 -0000

Hi
Thanks for your review! I include your comments for the next version of the
draft.

Comments inline:

|  -----Mensaje original-----
|  De: shim6-bounces@ietf.org [mailto:shim6-bounces@ietf.org] En nombre de
|  Brian E Carpenter
|  Enviado el: martes, 05 de octubre de 2010 1:51
|  Para: Geoff Huston
|  CC: shim6-chairs@tools.ietf.org;
draft-ietf-shim6-applicability@tools.ietf.org;
|  shim6
|  Asunto: Re: [shim6] Working Group Last Call
draft-ietf-shim6-applicability
|  
|  Hi,
|  
|  I believe this draft is ready for the IESG. I've noted some minor
|  points below, which could be fixed now or later.
|  
|       Brian
|  
|  Nits and editorial:
|  ===================
|  
|  >    This document may contain material from IETF Documents or IETF
|  >    Contributions published or made publicly available before November
|  >    10, 2008.
|  
|  Do we need this bit of legal junk? Unless there is specific old
|  material and its authors are not available to say "OK", there is
|  no need for this. So which old material written by who is included?

Yes, we don't need this part. I change the ipr claim so that this does not
appear.


|  
|  > Regarding to the outbound traffic to H,
|  
|  --> Regarding the outbound traffic to H,
|  
|  > IPv4 addressed can be
|  
|  --> IPv4 addresses can be
|  
|  >    [RFC3704] proposes that non-PI addresses should ensure that each
|  >    packet is delivered to the provider related with the prefix of its
|  >    source address.
|  
|  This is very contorted English. Maybe:
|  
|     [RFC3704] requires that sites using non-PI addresses should ensure
that each
|     packet is delivered to the provider whose prefix matches its source
address.
|  
|  >   These routers maintain as many parallel routing tables
|  >    as valid source prefixes are,
|  
|  --> These routers maintain as many parallel routing tables
|     as there are valid source prefixes,
|  
|  >    It is worth to note that
|  
|  --> It is worth noting that
|  
|  >   In particular, the use of HBA/CGA prevents on-path and
|  >    off-path attackers to introduce new locators in the locator set of a
|  >    Shim6 context, preventing redirection attacks [RFC4218].
|  
|  --> In particular, the use of HBA/CGA prevents on-path and
|     off-path attackers injecting new locators into the locator set of a
|     Shim6 context, thus preventing redirection attacks [RFC4218].

Made all these changes, thanks again


|  
|    == Outdated reference: A later version (-02) exists of
|       draft-nordmark-shim6-esd-01

Umm. I have a problem with this. I had already noticed that the 'nits' shown
by the IETF tools show 
  == Outdated reference: A later version (-02) exists of
     draft-nordmark-shim6-esd-01 

However, when I look for the -02 document, I cannot find it. For example,
https://datatracker.ietf.org/doc/draft-nordmark-shim6-esd/ refers to version
-01
In tools.ietf.org, only -01 is available
(http://tools.ietf.org/id/draft-nordmark-shim6-esd-01.txt - if 02 is tried,
it is redirected to 01)
Google cannot find the document for me, too.
So, it is not clear to me whether I should use 01 or 02 in the citation.

Regards,
Alberto

|  
|  _______________________________________________
|  shim6 mailing list
|  shim6@ietf.org
|  https://www.ietf.org/mailman/listinfo/shim6