Re: [v6ops] New Version Notification for draft-patterson-intarea-ipoe-health-01.txt

"Bernie Volz (volz)" <volz@cisco.com> Tue, 12 June 2018 15:32 UTC

Return-Path: <volz@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62A34124C04 for <v6ops@ietfa.amsl.com>; Tue, 12 Jun 2018 08:32:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 DAt9CqW5zUvi for <v6ops@ietfa.amsl.com>; Tue, 12 Jun 2018 08:32:14 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34846130E54 for <v6ops@ietf.org>; Tue, 12 Jun 2018 08:32:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8676; q=dns/txt; s=iport; t=1528817532; x=1530027132; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=5cKFvaMbJo4xLiCEeYHCffGz5pMaHat8QoyDnieIL0s=; b=fcyUmGGWIERLRIiTM5WA6aMpJHHWWYJ9jlLCbbBDwz05tVawgQdYu3wh Plr4St8D6hqlYKhmy4LebTxMw/EHv3IShjBCzXqRoYPvrvrfOwQvndvH/ b84UMrYgGHIZegF2yDsD1aU7mygjcBc9xOzQsuAUQwqVB6dO7waytoZ7L s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DeAAAX5x9b/5ldJa1cGQEBAQEBAQEBAQEBAQcBAQEBAYNDYn8oCoNtiASMaIFeIZRbgXgLGAuESQIXghshNBgBAgEBAQEBAQJtHAyFKAEBAQEDAQEhEToJDgQCAQgRBAEBAQICIwMCAgIlCxQBCAgCBAESgyICgX8PqnKCHIhHgWiBC4c9ghOBDyQMglyDEQEBAgEXgTAWF4JpMYIkAow2hQCHUAkChXGJBoE/QYM9h3WKCYcIAhETAYEkHTiBUnAVGiEqAYIYCYITLYM0hRSFPm+NUCuBAYEaAQE
X-IronPort-AV: E=Sophos;i="5.51,215,1526342400"; d="scan'208";a="407252865"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jun 2018 15:31:57 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w5CFVvjh022037 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 12 Jun 2018 15:31:57 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 12 Jun 2018 10:31:56 -0500
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1320.000; Tue, 12 Jun 2018 10:31:56 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>, Richard Patterson <richard@helix.net.nz>, "v6ops@ietf.org list" <v6ops@ietf.org>
Thread-Topic: [v6ops] New Version Notification for draft-patterson-intarea-ipoe-health-01.txt
Thread-Index: AQHUAj4k3JEcdK9gAkWXGzYu/zb6qqRdDTwA///EBAA=
Date: Tue, 12 Jun 2018 15:31:56 +0000
Message-ID: <2E94C78D-DC5E-4862-A493-A8E56A949FA2@cisco.com>
References: <152879468653.17363.11481811039500870007.idtracker@ietfa.amsl.com> <E896EC85-F967-401C-B52D-E0425A278188@sky.uk> <CAHL_VyDGX-fN=YJ9tkLaHHL+cVh0zyZ-WZwB=wrV9HSKSd84OA@mail.gmail.com> <9142206A0C5BF24CB22755C8EC422E459CB08340@AZ-US1EXMB03.global.avaya.com>
In-Reply-To: <9142206A0C5BF24CB22755C8EC422E459CB08340@AZ-US1EXMB03.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.22.0.170515
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.241.95]
Content-Type: text/plain; charset="utf-8"
Content-ID: <933F31240768A043B9ED5681FC04D3CA@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/V8lSm6owGK2VbYUBpGunfFoSb6w>
Subject: Re: [v6ops] New Version Notification for draft-patterson-intarea-ipoe-health-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2018 15:32:21 -0000

>    - If yes, is DHCPv6 client going to send the same address in SOLICIT? Is DHCPv6 client going to unicast SOLICIT to the same DHCPv6 server, if OPTION_UNICAST was set for the lease?
 
SOLICITs must not be unicast.

See https://tools.ietf.org/html/draft-ietf-dhc-rfc3315bis-13#section-16:

   A server MUST discard any Solicit, Confirm, Rebind or Information-
   request messages it receives with a layer-3 unicast destination
   address.

A client can certainly include the address it previously had in a Solicit (though most likely if the same server is present, that is not necessary as the server will likely use the existing address). There are also privacy considerations for including this in the Solicit (since the client may have moved to a different network).

- Bernie

On 6/12/18, 11:06 AM, "v6ops on behalf of Mudric, Dusan (Dusan)" <v6ops-bounces@ietf.org on behalf of dmudric@avaya.com> wrote:

    Hi Richard,
    
    "4.3.  Behaviour 2: Expire Lease"
    
    Typo: Behavior
    
    - Is this option an attempt for the lease RENEW-al but not using RENEW?
    - If not, what is the benefit of not sending RELEASE? 
    - If yes, is DHCPv6 client going to send the same address in SOLICIT? Is DHCPv6 client going to unicast SOLICIT to the same DHCPv6 server, if OPTION_UNICAST was set for the lease?
    
    Thanks,
    Dusan.
    
    > -----Original Message-----
    > From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Richard
    > Patterson
    > Sent: Tuesday, June 12, 2018 7:11 AM
    > To: v6ops@ietf.org list <v6ops@ietf.org>
    > Subject: [v6ops] New Version Notification for draft-patterson-intarea-ipoe-
    > health-01.txt
    > 
    > A new version of draft-patterson-intarea-ipoe-health has been posted.
    > 
    > The major change since -00, is the inclusion and preference of BFD
    > Echo as the health check mechanism when available.
    > The draft now has an informational reference to Broadband Forum's
    > TR-146 document which also discusses this problem.
    > 
    > The authors believe that this draft builds on the method suggested in
    > TR-146 in the following ways:
    > - Prefers BFD Echo, but allows for ARP/ND methods when not available.
    > - Defaults to DHCP renew as an action, but specifies optional
    > alternative actions to expedite recovery.
    > - Provides a DHCP Option to allow network administrators to signal
    > parameters dynamically to CEs.
    > 
    > 
    > On 12/06/2018, 10:11, "internet-drafts@ietf.org"
    > <internet-drafts@ietf.org> wrote:
    > 
    > 
    >     A new version of I-D, draft-patterson-intarea-ipoe-health-01.txt
    >     has been successfully submitted by Richard Patterson and posted to the
    >     IETF repository.
    > 
    >     Name:draft-patterson-intarea-ipoe-health
    >     Revision:01
    >     Title:IPoE Client Health Checking
    >     Document date:2018-06-12
    >     Group:Individual Submission
    >     Pages:12
    >     URL:
    > https://urldefense.proofpoint.com/v2/url?u=https-
    > 3A__www.ietf.org_internet-2Ddrafts_draft-2Dpatterson-2Dintarea-2Dipoe-
    > 2Dhealth-
    > 2D01.txt&d=DwIGaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=UT3Bk9cbLeaJxhf3iC
    > rhIoUWB8YLZU23029sMQGQ2kY&m=EBdxMMCB_3bhRx7Mk5RhobLPuxgDn
    > mbU6VSjpN4g1BY&s=bjBu9v7AUFYPKnWlcbMcpVAUCBAQAQkjarrZ0rAAUM
    > s&e=
    >     Status:
    > https://urldefense.proofpoint.com/v2/url?u=https-
    > 3A__datatracker.ietf.org_doc_draft-2Dpatterson-2Dintarea-2Dipoe-
    > 2Dhealth_&d=DwIGaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=UT3Bk9cbLeaJxhf3
    > iCrhIoUWB8YLZU23029sMQGQ2kY&m=EBdxMMCB_3bhRx7Mk5RhobLPuxgD
    > nmbU6VSjpN4g1BY&s=dpxyyPBoO4A6BEutg0KaTT2q1PFWSUd9xsjOPqel58s
    > &e=
    >     Htmlized:
    > https://urldefense.proofpoint.com/v2/url?u=https-
    > 3A__tools.ietf.org_html_draft-2Dpatterson-2Dintarea-2Dipoe-2Dhealth-
    > 2D01&d=DwIGaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=UT3Bk9cbLeaJxhf3iCrhI
    > oUWB8YLZU23029sMQGQ2kY&m=EBdxMMCB_3bhRx7Mk5RhobLPuxgDnmb
    > U6VSjpN4g1BY&s=ThEknV5dGWD2dWjPit9UcR0zTReSLb_HDbhDFN6SyCU&e
    > =
    >     Htmlized:
    > https://urldefense.proofpoint.com/v2/url?u=https-
    > 3A__datatracker.ietf.org_doc_html_draft-2Dpatterson-2Dintarea-2Dipoe-
    > 2Dhealth&d=DwIGaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=UT3Bk9cbLeaJxhf3i
    > CrhIoUWB8YLZU23029sMQGQ2kY&m=EBdxMMCB_3bhRx7Mk5RhobLPuxgD
    > nmbU6VSjpN4g1BY&s=wL3Cutrjzfyx5SLpM8qVzG4FHPxZoUkqzriELn3kuLM&
    > e=
    >     Diff:
    > https://urldefense.proofpoint.com/v2/url?u=https-
    > 3A__www.ietf.org_rfcdiff-3Furl2-3Ddraft-2Dpatterson-2Dintarea-2Dipoe-
    > 2Dhealth-
    > 2D01&d=DwIGaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=UT3Bk9cbLeaJxhf3iCrhI
    > oUWB8YLZU23029sMQGQ2kY&m=EBdxMMCB_3bhRx7Mk5RhobLPuxgDnmb
    > U6VSjpN4g1BY&s=cxcZ0tpDBRZc1iXSIKE9riKY-d6uMoShAsUvtPxFVTE&e=
    > 
    >     Abstract:
    >        PPP over Ethernet clients have the functionality to detect path
    >        unavailability by using PPP Keepalives.  IP over Ethernet does not
    >        have this functionality, and it's not specified when an IP over
    >        Ethernet client should consider its WAN connectivity down, unless
    >        there is a physical layer link down event.
    > 
    >        This document describes a way for IP over Ethernet clients to achieve
    >        connectivity validation, similar to that of PPP over Ethernet, by
    >        using BFD Echo, or ARP and Neighbor Discovery functions.
    > 
    > 
    > 
    > 
    >     Please note that it may take a couple of minutes from the time of
    > submission
    >     until the htmlized version and diff are available at tools.ietf.org.
    > 
    >     The IETF Secretariat
    > 
    > _______________________________________________
    > v6ops mailing list
    > v6ops@ietf.org
    > https://urldefense.proofpoint.com/v2/url?u=https-
    > 3A__www.ietf.org_mailman_listinfo_v6ops&d=DwIGaQ&c=BFpWQw8bsuKp
    > l1SgiZH64Q&r=UT3Bk9cbLeaJxhf3iCrhIoUWB8YLZU23029sMQGQ2kY&m=EBd
    > xMMCB_3bhRx7Mk5RhobLPuxgDnmbU6VSjpN4g1BY&s=geRPXtDiGajRjqb31
    > HRjp1le3zrflYjy6yhXPDSBouc&e=
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops