[MEXT] New Submission Notification for draft-yan-mext-dnsmip-00.txt
"yanzhiwei" <yanzhiwei@cnnic.cn> Tue, 25 October 2011 00:45 UTC
Return-Path: <yanzhiwei@cnnic.cn>
X-Original-To: mext@ietfa.amsl.com
Delivered-To: mext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id 84BA711E80DB for <mext@ietfa.amsl.com>;
Mon, 24 Oct 2011 17:45:46 -0700 (PDT)
X-Quarantine-ID: <yGLUMVHc59er>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: 2.558
X-Spam-Level: **
X-Spam-Status: No,
score=2.558 tagged_above=-999 required=5 tests=[BAYES_50=0.001,
HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MSGID_FROM_MTA_HEADER=0.803]
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 yGLUMVHc59er for
<mext@ietfa.amsl.com>; Mon, 24 Oct 2011 17:45:46 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by ietfa.amsl.com
(Postfix) with SMTP id 6D19821F8C98 for <mext@ietf.org>;
Mon, 24 Oct 2011 17:45:43 -0700 (PDT)
Received: (eyou send program); Tue, 25 Oct 2011 08:45:42 +0800
Message-ID: <519503542.27702@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yanzhiwei@cnnic.cn
Received: from unknown (HELO lenovo-think) (218.241.111.47) by 159.226.7.146
with SMTP; Tue, 25 Oct 2011 08:45:42 +0800
Date: Tue, 25 Oct 2011 08:45:42 +0800
From: "yanzhiwei" <yanzhiwei@cnnic.cn>
To: "mext" <mext@ietf.org>
References: <519482887.26346@cnnic.cn>
Message-ID: <201110250845425045760@cnnic.cn>
X-mailer: Foxmail 6, 15, 201, 22 [cn]
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=====001_Dragon453564210722_====="
Subject: [MEXT] New Submission Notification for draft-yan-mext-dnsmip-00.txt
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mext>,
<mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>,
<mailto:mext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Oct 2011 00:45:46 -0000
Dear all. I would like to let you know a new draft submitted: "draft-yan-mext-dnsmip-00.txt". The draft specifies the DNS update extension to Mobile IPv6 for the named MN. Specifically speaking, the FQND Option defined in the RFC 4704 is included in the Mobile IPv6 BU signaling message. The DNS update extension has been addressed in RFC 5026. The recommended mechanism from RFC 5026 is that the DNS update should be executed by the HA or AAA server, but not considering the MN's DNS update. In addition, it do not describe the PTR RR update processing. The proposed mechanism is based on RFC 4704 and covers the limitation of the DNS update of RFC 5026. Any comments are welcome. Zhiwei Yan 2011-10-25 yanzhiwei