Fwd: New Version Notification for draft-liu-6man-ident-tunnel-packet-addr-00.txt
Cong Liu <gnocuil@gmail.com> Mon, 21 October 2013 21:19 UTC
Return-Path: <gnocuil@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66A5E11E827B for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 14:19:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SQMXnwdRr07X for <ipv6@ietfa.amsl.com>; Mon, 21 Oct 2013 14:19:41 -0700 (PDT)
Received: from mail-qe0-x22c.google.com (mail-qe0-x22c.google.com [IPv6:2607:f8b0:400d:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 945E611E8269 for <ipv6@ietf.org>; Mon, 21 Oct 2013 14:19:41 -0700 (PDT)
Received: by mail-qe0-f44.google.com with SMTP id 6so4234126qeb.31 for <ipv6@ietf.org>; Mon, 21 Oct 2013 14:19:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=Gui2k4T+zjvWfhMaMCLZJEtoju7bKWIw7+e5yh8kIpk=; b=LFM2KzV2/z2WZMatKFf4sHFm5VQXqxnH/LmHBSR3qnFpfODdx6DSpRlL3vldeKrIZT kqNdJdjITUdo+UKBWoPsZrWDBeReasFTD03qY0sgm3E23Ggn2vnm4Qtp5nOK7X7xmct9 XBM8w9PeNPatUqFGKbRRbLCQyNPxGbycsBpmdNJDcUCKZzb0WDM4JfbbggV9rh+Wpj9G AeuE+IxCk8CaFssr3nN14wivxZllX4ImFS3HQ+MN822snL0xprPaN1S5hiRK1e8qoB9K djAXlBVBgFWA1xEKIKdvA8niuZOgvLihrvwxY5zF5QN5hs5cx+g8UCTJYwIcUnbXb+UV khgQ==
X-Received: by 10.49.131.200 with SMTP id oo8mr25788385qeb.0.1382390380889; Mon, 21 Oct 2013 14:19:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.96.185.33 with HTTP; Mon, 21 Oct 2013 14:19:20 -0700 (PDT)
In-Reply-To: <20131021182214.32521.22673.idtracker@ietfa.amsl.com>
References: <20131021182214.32521.22673.idtracker@ietfa.amsl.com>
From: Cong Liu <gnocuil@gmail.com>
Date: Tue, 22 Oct 2013 05:19:20 +0800
Message-ID: <CAF+sHxFeVnvQM-JC+gt=7MDtP5Hxwzp+i5UhMwF8g-+6oMW2tw@mail.gmail.com>
Subject: Fwd: New Version Notification for draft-liu-6man-ident-tunnel-packet-addr-00.txt
To: ipv6@ietf.org
Content-Type: multipart/alternative; boundary="047d7bdc8afe980cf404e946d7c7"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Oct 2013 21:19:42 -0000
Dear all, We have submitted a new draft proposes how a IPv6 tunnel node identifies inbound tunnel packets. We appreciate any comments and questions. Cong Liu ---------- Forwarded message ---------- From: <internet-drafts@ietf.org> Date: 2013/10/22 Subject: New Version Notification for draft-liu-6man-ident-tunnel-packet-addr-00.txt To: Jianping Wu <jianping@cernet.edu.cn>, Cong Liu <gnocuil@gmail.com>, Yong Cui <yong@csnet1.cs.tsinghua.edu.cn> A new version of I-D, draft-liu-6man-ident-tunnel-packet-addr-00.txt has been successfully submitted by Jianping Wu and posted to the IETF repository. Filename: draft-liu-6man-ident-tunnel-packet-addr Revision: 00 Title: Identifying Addresses of IPv6 Tunnel Packets at Tunnel Exit-point Creation date: 2013-10-21 Group: Individual Submission Number of pages: 6 URL: http://www.ietf.org/internet-drafts/draft-liu-6man-ident-tunnel-packet-addr-00.txt Status: http://datatracker.ietf.org/doc/draft-liu-6man-ident-tunnel-packet-addr Htmlized: http://tools.ietf.org/html/draft-liu-6man-ident-tunnel-packet-addr-00 Abstract: In the networks where IPv6 tunneling is used, it is not specific about how a tunnel end-node identifies the received tunnel packets by checking the destination and source addresses. when the tunnel end- node is configured with multiple IPv6 addresses or multiple IPv6 tunnel instances, such identification is necessary. This document describes the problem and defines the behavior of IPv6 tunnel end- nodes about identifying tunnel packets. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat