Re: New Liaison Statement, "LS on indicating service continuity usage of the additional IPv6 prefix in Router Advertisement"
Erik Kline <ek@google.com> Fri, 23 March 2018 01:11 UTC
Return-Path: <ek@google.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 3BA4F12711D for <ipv6@ietfa.amsl.com>; Thu, 22 Mar 2018 18:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 u5EaYqmZAGic for <ipv6@ietfa.amsl.com>; Thu, 22 Mar 2018 18:11:05 -0700 (PDT)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEB42127058 for <ipv6@ietf.org>; Thu, 22 Mar 2018 18:11:03 -0700 (PDT)
Received: by mail-wm0-x22b.google.com with SMTP id x82so806463wmg.1 for <ipv6@ietf.org>; Thu, 22 Mar 2018 18:11:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hlquxXJTgmQW0u5I+XTIxli5OKjwMNzEpfJI+Pqw/48=; b=Tx3bkV/2kwrex402lxK7C/4mSAevlbUD7q01KkAa0gEeo0uVDL8WAo33ZZdacy/Rjo nspto7UEvCwWcTdRlbsCbHLlvI9IaDVxMODSU67c9ffTwZV/bAzv2gwRWUMyN4KVh8+U JoFZZyfzNkiRk7Q30oHEn35KsZPTD/hQjLh4M47MCchYrsMyK7o24+2bbNn67zn1DRXA vFBQydvyqNcpSYx9v328AaGywH6KLMUlS6YwyH64vMNe/fiIXyW+cfK25gc1xSSguhVl RBdtTi3aTUprnr6Fg5P1suiMvHMilWvSpGpAt5qktPpsmSjM5z7N1LvTViqoNVf6mN8W bLkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hlquxXJTgmQW0u5I+XTIxli5OKjwMNzEpfJI+Pqw/48=; b=OAycAb6HCR0rMo/TdtlR81OtIYHkej32hn5NUE/mzGGcFlG2RijCv76OnklvsRYlHy 3Cqb192Atm1tlGyEAF8hEP7kVrkZbBLswjNJur/keOPOzE4fQfPwIKFj4ClMRaQxUleB ZpPjihbuKKLzRw0grNPP6liiv6k6kmjZUW35fh7+fh0sWumlthD6OD20bP5Ma/IvkxYG 0A7qK4+YAcw5m3lyonN+On8zzy4+KffdB88g/hKJZ+Kx81cIpLioQuS82s6z6M9js+WZ zidXQznt6M5iASoTJLcTjNHNVLZJC9IAswHmoh3+ccvAVkRQMZz2YWCs+HTXWckeTQfm uzIw==
X-Gm-Message-State: AElRT7H9zKfYN4RxjEXCtHQSkZWMjP3lIW0pSRlv60z8ws61JlSjzu9V obxZr3L29DeS1PQU70sa4zOjuTfjzCLNVwRGnGuCFw==
X-Google-Smtp-Source: AG47ELtoQlYSmcJAA1rR+T3XW8oxftv9Xhy2B/AaEUBKEyhz4L2dORclVnaEPx0FnVjewHfq6QaOymgy7k5SBl6ZI04=
X-Received: by 10.28.13.67 with SMTP id 64mr6629673wmn.5.1521767462140; Thu, 22 Mar 2018 18:11:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.231.16 with HTTP; Thu, 22 Mar 2018 18:10:38 -0700 (PDT)
In-Reply-To: <D69A2338.2A3B74%sgundave@cisco.com>
References: <151614272808.15844.15510087701780536192.idtracker@ietfa.amsl.com> <D69A2338.2A3B74%sgundave@cisco.com>
From: Erik Kline <ek@google.com>
Date: Thu, 22 Mar 2018 18:10:38 -0700
Message-ID: <CAAedzxqQt-8_ej_y8STq22hwMJuTZutyhdEQ-A=XXqCFdVbyVA@mail.gmail.com>
Subject: Re: New Liaison Statement, "LS on indicating service continuity usage of the additional IPv6 prefix in Router Advertisement"
To: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
Cc: Liaison Statement Management Tool <lsmt@ietf.org>, Dapeng Liu <maxpassion@gmail.com>, Terry Manderson <terry.manderson@icann.org>, Ole Troan <otroan@employees.org>, Robert Hinden <bob.hinden@gmail.com>, Suresh Krishnan <suresh@kaloom.com>, IPv6 Maintenance Discussion List <ipv6@ietf.org>, "3GPPLiaison@etsi.org" <3GPPLiaison@etsi.org>, "georg.mayer.huawei@gmx.com" <georg.mayer.huawei@gmx.com>, The IETF Chair <chair@ietf.org>, Distributed Mobility Management Discussion List <dmm@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="001a114436720af6bc05680a19e2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ML3IAznuf1naQtq7nmNGwTAAu_o>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 23 Mar 2018 01:11:07 -0000
> Also, some proposals from the previous years, which may be related: > > https://www.ietf.org/archive/id/draft-ietf-mif-mpvd-ndp-support-03.txt > https://www.ietf.org/archive/id/draft-ietf-mif-mpvd-id-02.txt There's also the existing PvD work in int-area. I think PvDs may work well for this...
- Re: New Liaison Statement, "LS on indicating serv… Sri Gundavelli (sgundave)
- Re: New Liaison Statement, "LS on indicating serv… Erik Kline