IETF Logo Mail Archive

Re: [pcp] #75 (third-party-id-option): Dave Thaler's comments on draft-ietf-pcp-third-party-id-option-00

"pcp issue tracker" <trac@tools.ietf.org> Tue, 01 September 2015 20:22 UTC

Return-Path: <trac@tools.ietf.org>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2E871B3865 for <pcp@ietfa.amsl.com>; Tue, 1 Sep 2015 13:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.31
X-Spam-Level:
X-Spam-Status: No, score=-1.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_64=0.6, T_RP_MATCHES_RCVD=-0.01] autolearn=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 fJ32ssqygBgO for <pcp@ietfa.amsl.com>; Tue, 1 Sep 2015 13:22:13 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (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 D2FDA1B2D95 for <pcp@ietf.org>; Tue, 1 Sep 2015 13:22:13 -0700 (PDT)
Received: from localhost ([::1]:33243 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac@tools.ietf.org>) id 1ZWs4I-0001Qc-2C; Tue, 01 Sep 2015 13:22:10 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: pcp issue tracker <trac@tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: draft-ietf-pcp-third-party-id-option@tools.ietf.org, rapenno@yahoo.com, quittek@neclab.eu
X-Trac-Project: pcp
Date: Tue, 01 Sep 2015 20:22:10 -0000
X-URL: http://tools.ietf.org/pcp/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/pcp/trac/ticket/75#comment:2
Message-ID: <074.96219c5eadcd00909ee3943623d0d235@tools.ietf.org>
References: <059.b391db7d29982cc510d59e4791c48b07@tools.ietf.org>
X-Trac-Ticket-ID: 75
In-Reply-To: <059.b391db7d29982cc510d59e4791c48b07@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-pcp-third-party-id-option@tools.ietf.org, rapenno@yahoo.com, quittek@neclab.eu, pcp@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: draft-ietf-pcp-third-party-id-option@ietf.org
Resent-Message-Id: <20150901202213.D2FDA1B2D95@ietfa.amsl.com>
Resent-Date: Tue, 01 Sep 2015 13:22:13 -0700
Resent-From: trac@tools.ietf.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/pcp/-wKsLCjUoN1orv77_NH0AVRH7AA>
Cc: pcp@ietf.org
Subject: Re: [pcp] #75 (third-party-id-option): Dave Thaler's comments on draft-ietf-pcp-third-party-id-option-00
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2015 20:22:15 -0000

#75: Dave Thaler's comments on draft-ietf-pcp-third-party-id-option-00


Comment (by quittek@neclab.eu):

 on 1) When the term "tunnel ID" is used in the text, it refers to example
 scenarios where indeed the THIRD_PARTY_ID is used as tunnel ID. I don't
 see how to avoid that without decreasing clarity of the text. Below please
 find all occurrences of the term "tunnel ID" in the draft. They all make
 sense:

 >    ... that the new THIRD_PARTY_ID serves in this scenario.  It
 >    carries the additional identifier, that is the tunnel ID ...

 >    To support the latter option, the BRAS needs to register the
 >    subscriber's tunnel IDs at the AAA Server at the time it contacts the
 >    AAA server for authentication and/or authorization of the subscriber.
 >    The tunnel IDs to be registered per subscriber at the AAA server may
 >    include the tunnel between CPE and BRAS, between BRAS and UPnP IGD-
 >    PCP IWF, and between BRAS and CGN.  The UPnP IGD-PCP IWF queries the
 >    AAA Server for the ID of the tunnel between BRAS and CGN, because
 >    this is the identifier to be used as the THIRD_PARTY_ID in the
 >    subsequent port mapping request.

 >    The Web Portal queries the AAA Server for the
 >    subscriber's tunnel ID of tunnel(BRAS, CGN) which was reported by the
 >    BRAS.  The returned tunnel ID of tunnel(BRAS, CGN) is used as the
 >    THIRD_PARTY_ID in the subsequent port mapping request.

 >    Despite the fact that above scenarios solely use tunnel IDs the
 >    THIRD_PARTY_ID can include any Layer-2 identifier like a MAC address
 >    or other subscriber identifiers as mentioned in section 6 of
 >    [I-D.boucadair-pcp-sfc-classifier-control].

 This should close this ticket.

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-pcp-third-party-id-
  dthaler@microsoft.com  |  option@tools.ietf.org
     Type:  defect       |      Status:  new
 Priority:  major        |   Milestone:  milestone1
Component:  third-       |     Version:  1.0
  party-id-option        |  Resolution:
 Severity:  In WG Last   |
  Call                   |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/pcp/trac/ticket/75#comment:2>
pcp <http://tools.ietf.org/pcp/>

v2.23.0 | Report a Bug | By Email