[FYI] I-D Action : draft-cha-ipv6-ra-mo-00.txt

HYUN WOOK CHA <hyunwook.cha@samsung.com> Mon, 09 June 2008 08:09 UTC

Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id 0D83828C0E5; Mon, 9 Jun 2008 01:09:05 -0700 (PDT)
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 95C713A6AC8; Mon, 9 Jun 2008 01:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.511
X-Spam-Status: No, score=-3.511 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, MIME_BASE64_BLANKS=0.041, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id 1M7TCOXpCEFD; Mon, 9 Jun 2008 01:09:02 -0700 (PDT)
Received: from mailout2.samsung.com (mailout2.samsung.com []) by core3.amsl.com (Postfix) with ESMTP id A44633A6AC4; Mon, 9 Jun 2008 01:09:02 -0700 (PDT)
Received: from ep_ms7_bk (mailout2.samsung.com []) by mailout2.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0K2600A2YRZ5NU@mailout2.samsung.com>; Mon, 09 Jun 2008 17:09:05 +0900 (KST)
Received: from ep_spt02 (ms7.samsung.com []) by ms7.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0K26008L6RZ5XJ@ms7.samsung.com>; Mon, 09 Jun 2008 17:09:05 +0900 (KST)
Content-return: prohibited
Date: Mon, 09 Jun 2008 08:09:05 +0000 (GMT)
From: HYUN WOOK CHA <hyunwook.cha@samsung.com>
Subject: [FYI] I-D Action : draft-cha-ipv6-ra-mo-00.txt
To: ipv6@ietf.org, dhcwg@ietf.org, =?euc-kr?Q?=C0=D3=C6=F2=BA=F3?= <pblim@samsung.com>
Message-id: <30925978.204361212998945070.JavaMail.weblogic@epml08>
MIME-version: 1.0
MIME-version: 1.0
X-Priority: 3
Msgkey: 20080609080619648@hyunwook.cha
X-MTR: 20080609080619648@hyunwook.cha
X-EPLocale: ko_KR.euc-kr
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-EPHeader: ML
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: hyunwook.cha@samsung.com
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Dear 6man and dhc folks,

Bernie Volz and I published an internet draft to clarify handling of M & O flags of IPv6 RA.
In this draft, we address operational problems regarding handling of M & O flags of RA in existing documents as below.
i) There is no method to revoke the operation of a DHCPv6 client invoked by IPv6 RA flags.  
ii) Per-interface state variables regarding availability of the DHCPv6 service cannot be maintained consistently in case that inconsistent M & O flags are contained in RAs sent by different routers.  
To solve these problems, this document describes a handling scheme of M & O flags in RA messages. which consists of an algorithm for the management of per-interface state variables and options regarding how these variables can be utilized to revoke DHCPv6 clients.

Please refer to the following URL.

We welcome any comments.

Thank you in advance.

Joseph HyunWook Cha

Software Engineer 
Network System Division 
SAMSUNG Electronics, Inc.

  If you do not stand firm in your faith, 
  you will not stand at all.  - Isaiah 7:9
IETF IPv6 working group mailing list
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6