Re: [ANCP] Inconsistency in draft-ietf-ancp-mc-extensions-16

Tom Taylor <tom.taylor.stds@gmail.com> Fri, 20 June 2014 19:22 UTC

Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: ancp@ietfa.amsl.com
Delivered-To: ancp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1B4D1B28DE for <ancp@ietfa.amsl.com>; Fri, 20 Jun 2014 12:22:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 i8Bj9oC5_nFl for <ancp@ietfa.amsl.com>; Fri, 20 Jun 2014 12:22:01 -0700 (PDT)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03F171B28ED for <ancp@ietf.org>; Fri, 20 Jun 2014 12:22:00 -0700 (PDT)
Received: by mail-ie0-f174.google.com with SMTP id lx4so3664931iec.33 for <ancp@ietf.org>; Fri, 20 Jun 2014 12:22:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Vm4e6gpbGDRZb4ReumxQvpmgeUWwll5EsaMJY6lAfCM=; b=HUf0nNcPXqnDsQ4ej4id89Jt/CWKM/ESos4q8ye7Q8m9cbMPUFJB6ZDzfqaRQRtGh6 nsqIZG8penMOArCiR30Q2CftLF/Y8TCwDpEIfx9NHDo50hn2/5oiFwepcZ1tvsLTCrWo +LerB5HO7Y1hl09jwQ7GElkf4tWrfyrYRl3epRt+Mal2XazZsLuaX7tXdP9HZ+nrR+Dl 4t6vlsRlGQrygoHBnmE/WPqGRlTbzOVddBzKAFnl3UJCT5RgVbcLqOcNl7jzURWFXf0a FU5rsAM2gkv1iAQgIQPWrrXMvALh/v1t9qSrBQH13bO5IMiJqmhsW4tK1w6EFLNe+QDO WBAQ==
X-Received: by 10.42.186.2 with SMTP id cq2mr6019194icb.25.1403292120398; Fri, 20 Jun 2014 12:22:00 -0700 (PDT)
Received: from [192.168.0.102] (dsl-173-206-0-110.tor.primus.ca. [173.206.0.110]) by mx.google.com with ESMTPSA id f9sm6723517igc.15.2014.06.20.12.21.59 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Jun 2014 12:22:00 -0700 (PDT)
Message-ID: <53A489D2.2040601@gmail.com>
Date: Fri, 20 Jun 2014 15:21:54 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Roberta Maglione (robmgl)" <robmgl@cisco.com>, "ancp@ietf.org" <ancp@ietf.org>, "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
References: <538F1897.1090702@gmail.com> <8A31814E-05BC-41F2-8484-3977A9CDE122@cisco.com> <CAKOT5KpVzDQBR9KkHCZEPZ-TmAL0WBz4iYRTSNDVx=QXCeURYw@mail.gmail.com> <57C3345230A4F94C9B2F5CFA05D7F2BD1EB9DE59@xmb-rcd-x01.cisco.com>
In-Reply-To: <57C3345230A4F94C9B2F5CFA05D7F2BD1EB9DE59@xmb-rcd-x01.cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ancp/5_JhAT-9n6aZRLr8qsv94TfEaoM
Subject: Re: [ANCP] Inconsistency in draft-ietf-ancp-mc-extensions-16
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp/>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jun 2014 19:22:04 -0000

I have made the following changes to the RFC Editor's version of the 
document. Basically they propagate the Section 4.2.2 text to Sections 
4.6.2.2 and 4.8.2.2, with an extra reference to procedures in 6.2.5.2.

In Section 4.6.2.2:

OLD

    If, as the result of the procedures just described, the AN determines
    that it has over-committed multicast bandwidth, it MUST NOT terminate
    any currently active programs but MUST NOT honor any more join
    requests until it is possible to do so within the limit set by its
    current value of delegated bandwidth.

NEW

    If the AN has already committed multicast bandwidth exceeding the
    amount given in the Bandwidth-Allocation TLV, the AN SHOULD NOT
    discontinue any multicast streams in order to bring bandwidth down to
    within the new limit, unless such action is required by local policy.
    However, the AN MUST NOT admit new multicast streams that are subject
    to admission control until it can do so within the limit specified by
    the Bandwidth-Allocation TLV.  As specified in Section 6.2.5.2, the
    AN MAY attempt to correct the situation by sending a request to the
    NAS for an increased allocation of delegated bandwidth using the
    Bandwidth Reallocation Request message.

In Section 4.8.2.2:

OLD

    If the AN has
    currently committed more than this amount to active programs, it MUST
    NOT cease replicating the flows concerned but MUST NOT honor any more
    join requests until possible to do so within the new limit.

NEW

    If the AN has
    already committed multicast bandwidth exceeding the amount given in
    the Bandwidth-Allocation TLV, the AN SHOULD NOT discontinue any
    multicast streams in order to bring bandwidth down to within the new
    limit, unless such action is required by local policy.  However, the
    AN MUST NOT admit new multicast streams that are subject to admission
    control until it can do so within the limit specified by the
    Bandwidth-Allocation TLV.  As specified in Section 6.2.5.2, the AN
    MAY attempt to correct the situation by sending a request to the NAS
    for an increased allocation of delegated bandwidth using the
    Bandwidth Reallocation Request message.

Tom Taylor

On 18/06/2014 8:34 AM, Roberta Maglione (robmgl) wrote:
> Tom, Francois and All,
>
> Sorry for my late reply, comments inline.
>
>>I would suggest that the AN first attempts to increase the delegated bandwidth by sending to the NAS a >Bandwidth Reallocation >Request message. This is the behavior already specified (1) for the AN in the  situation where the delegated bandwidth has not been >modified but
> there is a new multicast join that would result in committing more
> bandwidth than delegated.
>>Would you agree?
>
> I agree with this approach.
>
>>If this attempt does not result in obtaining sufficient bandwidth to avoid any over-commitment, I would recommend retaining the behavior >currently specified in 4.2.2 (ie "the AN SHOULD NOT discontinue any  multicast streams in order to bring bandwidth down to within the >new
> limit, unless such action is required by local policy.)  and align the
> text of teh sections that are inconsistent with that.
>
> In opinion it would make sense to maintain the behavior currently
> specified in 4.2.2 (ie "the AN SHOULD NOT discontinue any multicast
> streams in order to bring bandwidth down to within the >new limit,
> unless such action is required by local policy), therefore I would
> support the proposal of aligning all the sections with this behavior.
>
> Thanks
>
> Best Regards
>
> Roberta
>
> ---------- Forwarded message ----------
> From: *Francois Le Faucheur (flefauch)* <flefauch@cisco.com
> <mailto:flefauch@cisco.com>>
> Date: Wed, Jun 4, 2014 at 7:18 AM
> Subject: Re: [ANCP] Inconsistency in draft-ietf-ancp-mc-extensions-16
> To: Tom Taylor <tom.taylor.stds@gmail.com
> <mailto:tom.taylor.stds@gmail.com>>
> Cc: "ancp@ietf.org <mailto:ancp@ietf.org>" <ancp@ietf.org
> <mailto:ancp@ietf.org>>
>
>
> Tom and all,
>
> In the considered scenario where:
>          * the AN receives a new Bandwidth-Allocation TLV
>          * the AN has already committed more multicast bandwidth
> I would suggest that the AN first attempts to increase the delegated
> bandwidth by sending to the NAS a Bandwidth Reallocation Request
> message. This is the behavior already specified (1) for the AN in the
> situation where the delegated bandwidth has not been modified but there
> is a new multicast join that would result in committing more bandwidth
> than delegated.
> Would you agree?
>
> If this attempt does not result in obtaining sufficient bandwidth to
> avoid any over-commitment, I would recommend retaining the behavior
> currently specified in 4.2.2 (ie "the AN SHOULD NOT discontinue any
> multicast streams in order to bring bandwidth down to within the new
> limit, unless such action is required by local policy.)  and align the
> text of teh sections that are inconsistent with that.
>
>
> Francois
>
>
> (1) section 6.2.5.2. :
> “
> When the AN receives a join request, it
>     checks whether it has sufficient remaining uncommitted multicast
>     bandwidth on the access line to accommodate the new multicast flow.
>     If not, it MAY send a request to the NAS for an increased allocation
>     of delegated bandwidth using the Bandwidth Reallocation Request
>     message.  The NAS MUST return a Bandwidth Transfer message indicating
>     whether it has granted the request and, if so, the new amount of
>     delegated bandwidth.
>
> "
>
>
> On 4 Jun 2014, at 15:01, Tom Taylor <tom.taylor.stds@gmail.com
> <mailto:tom.taylor.stds@gmail.com>> wrote:
>
>  > Doing my AUTH48 review for draft-ietf-ancp-mc-extensions-16, I
> noticed an inconsistency in treatment between three different cases
> where the AN is assigned a value of multicast bandwidth that is lower
> than the AN has already committed to a given subscriber. The question to
> the Working Group is whether:
>  >  (a) no change is needed; or
>  >  (b) local policy should determine whether established connections
> should be taken down to meet bandwidth limits set by the NAS in all
> cases; or
>  >  (c) established connections should never be taken down until
> terminated by the subscriber (no provision for local policy in any case).
>  >
>  > The context in each instance is that the NAS has sent a multicast
> bandwidth allocation to the AN. If the AN does not conform to that
> allocation, the NAS does not have a correct view of the amount of
> bandwidth available for admission control (e.g., of unicast services) at
> the NAS itself. That should probably be fixed independently of the
> question stated above.  And, of course, the over-commitment at the AN
> means that less bandwidth is available for services admitted at the NAS.
>  >
>  > Here are the three cases in question:
>  >
>  > Case 1: bandwidth assigned by Port Management message
>  > =====================================================
>  >
>  > Receiver behaviour is described in Section 4.2.2. Note the provision
> for local policy in the quoted text:
>  >
>  >  "If the Port Management message contains a Bandwidth-Allocation TLV,
>  >   the AN adopts this as the current value of its total multicast
>  >   bandwidth limit for the target port.  If the AN has already committed
>  >   multicast bandwidth exceeding the amount given in the Bandwidth-
>  >   Allocation TLV, the AN SHOULD NOT discontinue any multicast streams
>  >   in order to bring bandwidth down to within the new limit, unless such
>  >   action is required by local policy.  However, the AN MUST NOT admit
>  >   new multicast streams that are subject to admission control until it
>  >   can do so within the limit specified by the Bandwidth-Allocation
>  >   TLV."
>  >
>  > Case 2: bandwidth assigned by Bandwidth Transfer message
>  > ========================================================
>  >
>  > AN behaviour as receiver is described in Section 4.6.2.2. There is no
> provision for local policy:
>  >
>  >  "If as the result of the procedures just described the AN determines
>  >   that it has over-committed multicast bandwidth, it MUST NOT terminate
>  >   any currently-active programs, but MUST NOT honour any more "join"
>  >   requests until it is possible to do so within the limit set by its
>  >   current value of delegated bandwidth."
>  >
>  > Case 3: bandwidth assigned by Delegated Bandwidth Query Response message
>  > ========================================================================
>  >
>  > AN behaviour as receiver is described in Section 4.8.2.2. There is no
> provision for local policy:
>  >
>  >  "... If the AN has
>  >   currently committed more than this amount to active programs, it MUST
>  >   NOT cease replicating the flows concerned, but MUST NOT honour any
>  >   more Join requests until possible to do so within the new limit."
>  >
>  >
>  > Tom Taylor
>  >
>  > _______________________________________________
>  > ANCP mailing list
>  > ANCP@ietf.org <mailto:ANCP@ietf.org>
>  > https://www.ietf.org/mailman/listinfo/ancp
>
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org <mailto:ANCP@ietf.org>
> https://www.ietf.org/mailman/listinfo/ancp
>