IETF Logo Mail Archive

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

S Moonesamy <sm+ietf@elandsys.com> Mon, 23 June 2014 20:07 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 62EF91B2C72 for <hipsec@ietfa.amsl.com>; Mon, 23 Jun 2014 13:07:05 -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 wS5mxUzC5AtK for <hipsec@ietfa.amsl.com>; Mon, 23 Jun 2014 13:06:59 -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 459361B2C4B for <hipsec@ietf.org>; Mon, 23 Jun 2014 13:06:57 -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 s5NK6fQw012256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Jun 2014 13:06:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1403554014; x=1403640414; bh=ffcCxBsxpaiywMkXoQg3nZsuTVPf+GPNifvUfRv9iM0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rs3fzQFU9rgtTfL2Qz7TqcwDzBadzstlt1UAwj/ZMlAuUxkSBLTJYSaCoqBOdWbDt SJlUBQa7DZjau7uHsdaLJ8zyGFmDoUXou3nFtYc4RKT36UQi8xsmuQoyjZf4v+/Mdm Sf+nxJ2nOmlZVAPer4eoC+J8oQiYR80Z6RYlxmK0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1403554014; x=1403640414; i=@elandsys.com; bh=ffcCxBsxpaiywMkXoQg3nZsuTVPf+GPNifvUfRv9iM0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=VCEOwX7vMXfR7Mny3iciztbp5F4eZQLWodWVfmlW1tMt8TY+ze1EsAdt9inRf12Nj kZ9XetRd8BnqbFqiOUo4ImbbEBn+ScmCovccWZqZIrWiNhgs/Kmzq6HtY3SJjKa2jx U8IFZ6y6hIM9sXDKipuRXhgV8gvUOMTZFp2NGYXI=
Message-Id: <6.2.5.6.2.20140623130454.0bbbccb8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 23 Jun 2014 13:06:16 -0700
To: Julien Laganier <julien.ietf@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <CAE_dhjvWTWkqHkvUx+pw+pKn5G1DH3KCM5P=-FPev_fXDMAMBg@mail.g mail.com>
References: <0B09A467-1447-4D61-804D-9DD581A89275@nominum.com> <6.2.5.6.2.20140623103438.0c2c1490@elandnews.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> <7826FE0A-C388-466A-94B9-1228973AFE9B@nominum.com> <CAE_dhjseo_fMUVEttPj+6TGtJr4yz+QhhgH=sjB02KtdUVDbeQ@mail.gmail.com> <6.2.5.6.2.20140623111840.0bbb9c08@elandnews.com> <CAE_dhjvWTWkqHkvUx+pw+pKn5G1DH3KCM5P=-FPev_fXDMAMBg@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/AVWh4d2117glMO9vWoZ_ITIXfe4
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 20:07:05 -0000

Hu Julien,
At 12:54 23-06-2014, Julien Laganier wrote:
>How about this then:
>
>"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, e.g., the ORCHID prefix can be blocked by
>  a simple configuration rule such as an Access Control List entry."

The above looks fine.

Regards,
S. Moonesamy

v2.46.0 | Report a Bug | By Email | System Status