RFC 6611 on Mobile IPv6 (MIPv6) Bootstrapping for the Integrated Scenario
rfc-editor@rfc-editor.org Tue, 15 May 2012 00:03 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1308A21F8969 for <ietf-announce@ietfa.amsl.com>; Mon, 14 May 2012 17:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.115
X-Spam-Level:
X-Spam-Status: No, score=-102.115 tagged_above=-999 required=5 tests=[AWL=-0.115, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 IpsHNfn6LsCC for <ietf-announce@ietfa.amsl.com>; Mon, 14 May 2012 17:03:27 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id A5A2221F896A for <ietf-announce@ietf.org>; Mon, 14 May 2012 17:03:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2A68DB1E00D; Mon, 14 May 2012 17:00:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6611 on Mobile IPv6 (MIPv6) Bootstrapping for the Integrated Scenario
From: rfc-editor@rfc-editor.org
Message-Id: <20120515000048.2A68DB1E00D@rfc-editor.org>
Date: Mon, 14 May 2012 17:00:48 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2012 00:03:28 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6611 Title: Mobile IPv6 (MIPv6) Bootstrapping for the Integrated Scenario Author: K. Chowdhury, Ed., A. Yegin Status: Standards Track Stream: IETF Date: May 2012 Mailbox: kc@radiomobiles.com, alper.yegin@yegin.org Pages: 12 Characters: 27152 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mip6-bootstrapping-integrated-dhc-06.txt URL: http://www.rfc-editor.org/rfc/rfc6611.txt Mobile IPv6 bootstrapping can be categorized into two primary scenarios: the split scenario and the integrated scenario. In the split scenario, the mobile node's mobility service is authorized by a different service authorizer than the network access authorizer. In the integrated scenario, the mobile node's mobility service is authorized by the same service authorizer as the network access service authorizer. This document defines a method for home agent information discovery for the integrated scenario. [STANDARDS-TRACK] This document is a product of the Mobility for IPv6 Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC