Re: [Hipsec] Last Call: <draft-ietf-hip-rfc4843-bis-05.txt> (An, etc.

S Moonesamy <sm+ietf@elandsys.com> Mon, 23 June 2014 18:42 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 755451B2C19 for <hipsec@ietfa.amsl.com>; Mon, 23 Jun 2014 11:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level:
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, T_DKIM_INVALID=0.01] 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 2svUm1UqWgqf for <hipsec@ietfa.amsl.com>; Mon, 23 Jun 2014 11:42:51 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 64A0C1B2BD2 for <hipsec@ietf.org>; Mon, 23 Jun 2014 11:42:44 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.135.167]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s5NIgNF9026702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Jun 2014 11:42:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1403548956; x=1403635356; bh=iXK8dGMK5kWGCtFk3W+vsjGe9YzrMcMNU2xEybWH/Bc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2mBsZan/6UNU3cMn392P60TZZUiAS1hPiXj0O+OiEOYm7hXXFGnGMjk5dXGB2Wqtx azqCgnddTacYRit4uyuC0LkKiOa2LV1/uru6jT+JVC8rPkPYepos57OKxtnU8emNDm zEnQM79k9tGYEkEhK0Io9HUu32dy/BTbLUY3s3FI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1403548956; x=1403635356; i=@elandsys.com; bh=iXK8dGMK5kWGCtFk3W+vsjGe9YzrMcMNU2xEybWH/Bc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=jN/EuabXIe6vL44mNksVvkBqBGnUCjgpSHta/HRo7KhmuYHc3zTCyNJmfZuWxMgg7 NoPuskduy2P0oLuEZ0aSfamlx1SHPGH6tQgWGjZ1sqrD3bYo9hh3UFi/+DZ4HvrtpR GJ5tROC04kvQkSllxlS9eVVptmch2ltZtLaKOlhA=
Message-Id: <6.2.5.6.2.20140623111840.0bbb9c08@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 23 Jun 2014 11:41:40 -0700
To: Ted Lemon <ted.lemon@nominum.com>, Julien Laganier <julien.ietf@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <7826FE0A-C388-466A-94B9-1228973AFE9B@nominum.com> <CAE_dhjseo_fMUVEttPj+6TGtJr4yz+QhhgH=sjB02KtdUVDbeQ@mail.gmail.com>
References: <20140528160426.31345.98483.idtracker@ietfa.amsl.com> <6.2.5.6.2.20140607073853.0b975758@resistor.net> <CAE_dhju4kfj=YXjJN-rMXDNd-zLy4zLawf_2jcBh26CiFSJ99A@mail.gmail.com> <0B09A467-1447-4D61-804D-9DD581A89275@nominum.com> <6.2.5.6.2.20140623103438.0c2c1490@elandnews.com> <7826FE0A-C388-466A-94B9-1228973AFE9B@nominum.com> <20140528160426.31345.98483.idtracker@ietfa.amsl.com> <6.2.5.6.2.20140607073853.0b975758@resistor.net> <CAE_dhju4kfj=YXjJN-rMXDNd-zLy4zLawf_2jcBh26CiFSJ99A@mail.gmail.com> <6.2.5.6.2.20140623102349.0c2c19b0@elandnews.com> <CAE_dhjseo_fMUVEttPj+6TGtJr4yz+QhhgH=sjB02KtdUVDbeQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/hipsec/9kGi9BvNyYvzNkRNG1Z8k2IdyhQ
X-Mailman-Approved-At: Sun, 29 Jun 2014 23:51:18 -0700
Cc: hipsec@ietf.org, Francis Dupont <fdupont@isc.org>
Subject: Re: [Hipsec] Last Call: <draft-ietf-hip-rfc4843-bis-05.txt> (An, etc.
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 18:42:52 -0000

Hi Ted,
At 10:44 23-06-2014, Ted Lemon wrote:
>Fair enough.   Do you think the text as written will create 
>interoperability problems?

I would say avoid that type of phrasing as it may lead to problems.

At 10:45 23-06-2014, Julien Laganier wrote:
>How about this:
>
>"Router software MUST NOT include any special handling code for
>ORCHIDs.  In other words, the non-routability property of ORCHIDs, if
>implemented, is to be implemented via configuration rather than by
>hardwired software code.  At this time, it is RECOMMENDED that the
>default router configuration not handle ORCHIDs in any special way.
>In other words, there is no need to touch existing or new routers due
>to ORCHIDs.  If such a reason should later appear, for example, due
>to a faulty implementation leaking ORCHIDs to the IP layer, the
>prefix can be and should be blocked by a simple configuration rule such as,
>e.g., an Access Control List entry."

The first two sentences look fine.  I suggest trying to look at the 
"recommendation" part as something after the document is 
published.  I am not thinking clearly enough to suggest text. :-(  I 
would avoid the "should" in the last sentence.

Regards,
S. Moonesamy