[DMM] RFC 8653 on On-Demand Mobility Management

rfc-editor@rfc-editor.org Fri, 01 November 2019 04:39 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8EA41208A5; Thu, 31 Oct 2019 21:39:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 WRsIvkxIICWU; Thu, 31 Oct 2019 21:39:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B43C812085A; Thu, 31 Oct 2019 21:39:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8F4ACF406D7; Thu, 31 Oct 2019 21:39:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dmm@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20191101043922.8F4ACF406D7@rfc-editor.org>
Date: Thu, 31 Oct 2019 21:39:22 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/YkeknE441a73wNjKrrmA3cW-NxE>
Subject: [DMM] =?utf-8?q?RFC_8653_on_On-Demand_Mobility_Management?=
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Nov 2019 04:39:38 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8653

        Title:      On-Demand Mobility Management 
        Author:     A. Yegin, 
                    D. Moses,
                    S. Jeon
        Status:     Informational
        Stream:     IETF
        Date:       October 2019
        Mailbox:    alper.yegin@actility.com, 
                    danny.moses@intel.com, 
                    seiljeon.ietf@gmail.com
        Pages:      12
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dmm-ondemand-mobility-18.txt

        URL:        https://www.rfc-editor.org/info/rfc8653

        DOI:        10.17487/RFC8653

Applications differ with respect to whether they need session
continuity and/or IP address reachability. The network providing the
same type of service to any mobile host and any application running
on the host yields inefficiencies, as described in RFC 7333.  This
document defines a new concept of enabling applications to influence
the network's mobility services (session continuity and/or IP address
reachability) on a per-socket basis, and suggests extensions to the
networking stack's API to accommodate this concept.

This document is a product of the Distributed Mobility Management Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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