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

"Holland, Jake" <jholland@akamai.com> Fri, 06 January 2017 02:38 UTC

Return-Path: <jholland@akamai.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 8A2671296D2 for <mboned@ietfa.amsl.com>; Thu, 5 Jan 2017 18:38:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.801
X-Spam-Level:
X-Spam-Status: No, score=-5.801 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, RP_MATCHES_RCVD=-3.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=akamai.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 YzAPGweoKvyk for <mboned@ietfa.amsl.com>; Thu, 5 Jan 2017 18:38:52 -0800 (PST)
Received: from prod-mail-xrelay06.akamai.com (prod-mail-xrelay06.akamai.com [96.6.114.98]) by ietfa.amsl.com (Postfix) with ESMTP id 6A224129B1C for <mboned@ietf.org>; Thu, 5 Jan 2017 18:38:52 -0800 (PST)
Received: from prod-mail-xrelay06.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id D0077496C58; Fri, 6 Jan 2017 02:38:51 +0000 (GMT)
Received: from prod-mail-relay09.akamai.com (prod-mail-relay09.akamai.com [172.27.22.68]) by prod-mail-xrelay06.akamai.com (Postfix) with ESMTP id AFDD0496C55; Fri, 6 Jan 2017 02:38:51 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; s=a1; t=1483670331; bh=emP4o3MQ9Q9Bb+Sl3sDHjTJ1he78CSZwFSMyCofOVqk=; l=2184; h=From:To:CC:Date:References:In-Reply-To:From; b=uT4gM3lvlLzIx55PO3PrQNd7LWIgAJwzIwcJ0Il04/Oo4Wxc1hE4mWQnIlLEUj9ap GYQV5Oxkw4/A7f5ONbpI15jF/p/uAG2sgPnjAMWF1FxJmR2qXLXRTQRJKqtDP5HpE2 IZiGoKzxk484hLNN8CBZYHmIrvxkwogBTXHWbcxo=
Received: from email.msg.corp.akamai.com (usma1ex-cas1.msg.corp.akamai.com [172.27.123.30]) by prod-mail-relay09.akamai.com (Postfix) with ESMTP id 92E7F1E07C; Fri, 6 Jan 2017 02:38:51 +0000 (GMT)
Received: from usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) by usma1ex-dag1mb5.msg.corp.akamai.com (172.27.123.105) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 5 Jan 2017 21:38:50 -0500
Received: from usma1ex-dag1mb6.msg.corp.akamai.com ([172.27.123.65]) by usma1ex-dag1mb6.msg.corp.akamai.com ([172.27.123.65]) with mapi id 15.00.1178.000; Thu, 5 Jan 2017 18:38:50 -0800
From: "Holland, Jake" <jholland@akamai.com>
To: Stig Venaas <stig@venaas.com>, Greg Shepherd <gjshep@gmail.com>
Thread-Topic: [MBONED] WGLC: draft-ietf-mboned-interdomain-peering-bcp-06
Thread-Index: AQHSQa2uyFf9QYOcfkqhC9mdP2IB6aD6O6SAgAjpRwCAI+GagIAEE30A///up4A=
Date: Fri, 06 Jan 2017 02:38:50 +0000
Message-ID: <3B34E3AF-4182-4415-B775-0C84FE32A81C@akamai.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>
In-Reply-To: <CAHANBt+b2xmfsn+NSRbFx6-vN8N0PfmSZ8HULmc3+7zAG7jg5w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1b.0.161010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.113.199]
Content-Type: text/plain; charset="utf-8"
Content-ID: <B21800147A46C44F8E8B2D3DA8904189@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/ZbmG1yspfydsd8c2M5xWiv5u_pc>
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: Fri, 06 Jan 2017 02:38:54 -0000

On 1/5/17, 11:40 AM, "Stig Venaas" <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