IETF Logo Mail Archive

Re: [MBONED] WGLC: draft-ietf-mboned-interdomain-peering-bcp-06

"TARAPORE, PERCY S" <pt5947@att.com> Mon, 30 January 2017 21:03 UTC

Return-Path: <pt5947@att.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4707129606 for <mboned@ietfa.amsl.com>; Mon, 30 Jan 2017 13:03:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.755
X-Spam-Level:
X-Spam-Status: No, score=-3.755 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.156, 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 8VDu2DAtkKVf for <mboned@ietfa.amsl.com>; Mon, 30 Jan 2017 13:03:26 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 747921295FE for <mboned@ietf.org>; Mon, 30 Jan 2017 13:03:26 -0800 (PST)
Received: from pps.filterd (m0049462.ppops.net [127.0.0.1]) by m0049462.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v0UKtfeB041815; Mon, 30 Jan 2017 16:01:01 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049462.ppops.net-00191d01. with ESMTP id 28abm7anem-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 30 Jan 2017 16:01:00 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v0UL0vYl024793; Mon, 30 Jan 2017 16:00:59 -0500
Received: from mlpi409.sfdc.sbc.com (mlpi409.sfdc.sbc.com [130.9.128.241]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v0UL0a4S023200 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 30 Jan 2017 16:00:49 -0500
Received: from MISOUT7MSGHUBAG.ITServices.sbc.com (MISOUT7MSGHUBAG.itservices.sbc.com [130.9.129.151]) by mlpi409.sfdc.sbc.com (RSA Interceptor); Mon, 30 Jan 2017 21:00:18 GMT
Received: from MISOUT7MSGUSRDG.ITServices.sbc.com ([169.254.7.214]) by MISOUT7MSGHUBAG.ITServices.sbc.com ([130.9.129.151]) with mapi id 14.03.0319.002; Mon, 30 Jan 2017 16:00:17 -0500
From: "TARAPORE, PERCY S" <pt5947@att.com>
To: "Holland, Jake" <jholland@akamai.com>, Stig Venaas <stig@venaas.com>, Greg Shepherd <gjshep@gmail.com>
Thread-Topic: [MBONED] WGLC: draft-ietf-mboned-interdomain-peering-bcp-06
Thread-Index: AQHSTzWn79A6YQgRW0KFonLXkZzKm6ED8uQAgCLGR4CABBN8AIAAdMUAgCaUj5A=
Importance: high
X-Priority: 1
Date: Mon, 30 Jan 2017 21:00:17 +0000
Message-ID: <ACC789373DA69C4285B9678D0CEBF86F12D73F9E@MISOUT7MSGUSRDG.ITServices.sbc.com>
References: <CABFReBqbA8a6VMUUvg4TAbXJh1s4yyvjGgGw+DkV2A1Twe_Znw@mail.gmail.com> <CABFReBqsnuvt3rX2u2oG+ZciGyaOvVmx6HZ3CK9pWbat4ubbbw@mail.gmail.com> <410A3E0C-E521-475D-8525-8DB3AB454AEC@akamai.com> <CABFReBrtY5LpKGvr+71=kDFrpLsUWpayqWaXGHR-PoBpWCa4Fw@mail.gmail.com> <CAHANBt+b2xmfsn+NSRbFx6-vN8N0PfmSZ8HULmc3+7zAG7jg5w@mail.gmail.com> <3B34E3AF-4182-4415-B775-0C84FE32A81C@akamai.com>
In-Reply-To: <3B34E3AF-4182-4415-B775-0C84FE32A81C@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [135.16.234.231]
Content-Type: multipart/mixed; boundary="_004_ACC789373DA69C4285B9678D0CEBF86F12D73F9EMISOUT7MSGUSRDG_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-01-30_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1701300195
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/YdZbv1OvQi4o4dzJTx6dpJUQAx4>
Cc: "mboned@ietf.org" <mboned@ietf.org>
Subject: Re: [MBONED] WGLC: draft-ietf-mboned-interdomain-peering-bcp-06
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jan 2017 21:03:29 -0000

Jake & Stig,



Attached please find a revised marked up Draft BCP that addresses all your comments as follows:



Jake we accepted all your suggested revisions and have incorporated them into the text.



Stig, we attempted to address all your comments. Please review the changes associated with the revision proposed on page 18 (bottom of the page). These changes allow us to keep the text for the bullet on page 19 which was the motivation for Stig’s Comment 2. Please let us know if this is acceptable.



Please respond back to me by mid-week so I can formally upload the revised Draft and request start of the next – and hopefully last – Last Call.



Thank you for all your help.



Percy & Bob



-----Original Message-----
From: MBONED [mailto:mboned-bounces@ietf.org] On Behalf Of Holland, Jake
Sent: Thursday, January 05, 2017 9:39 PM
To: Stig Venaas <stig@venaas.com>; Greg Shepherd <gjshep@gmail.com>
Cc: mboned@ietf.org
Subject: Re: [MBONED] WGLC: draft-ietf-mboned-interdomain-peering-bcp-06



On 1/5/17, 11:40 AM, "Stig Venaas" <stig@venaas.com<mailto:stig@venaas.com>> wrote:

    I see in 4.2.3 it says:

      o Using the information from the metadata, and possibly information

         provisioned directly in the EU client, a DNS query is initiated in

         order to connect the EU client/AMT Gateway to an AMT Relay.



    Do we already have a solution that allows for choosing a different

    relay for different sources? I would be interested in more details. I

    guess it may be out of scope here. But is there already a way of

    describing this with metadata for any applications or EU clients? As a

    BCP it should ideally refer to things that already are in use.





The Octoshape media client does something that fits this description. The (S,G) and the relay address can be provisioned in the client based on metadata it receives at runtime. The DNS is optional, but in this context it’s an example, and I think this describes a real-life scenario that’s deployed today.





To be on the safe side, having mentioned the Octoshape client, I should probably make an IPR disclosure:

There are some patents related to the Octoshape technology that I believe are now owned by Akamai and/or its subsidiaries. Though I do not believe this nuance of configurable AMT relay discovery is covered in any of the claims, the Octoshape system itself does use some patent-encumbered technology, and if you are inspired to examine its behavior in light of this discussion or for some other reason, please be aware that you should consider the patents appropriately.



Cheers,

Jake





_______________________________________________

MBONED mailing list

MBONED@ietf.org<mailto:MBONED@ietf.org>

https://www.ietf.org/mailman/listinfo/mboned

v2.23.0 | Report a Bug | By Email