IETF Logo Mail Archive

[3gpp-ietf-coord] Fwd: [tsvwg] [QCI-Diffserv] Side meeting at the IETF Montreal - call for agenda items

"DOLLY, MARTIN C" <md3135@att.com> Tue, 23 July 2019 16:38 UTC

Return-Path: <md3135@att.com>
X-Original-To: 3gpp-ietf-coord@ietfa.amsl.com
Delivered-To: 3gpp-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13C45120356 for <3gpp-ietf-coord@ietfa.amsl.com>; Tue, 23 Jul 2019 09:38:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 cYqUSHZWcDYW for <3gpp-ietf-coord@ietfa.amsl.com>; Tue, 23 Jul 2019 09:38:22 -0700 (PDT)
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 9FDA1120282 for <3gpp-ietf-coord@ietf.org>; Tue, 23 Jul 2019 09:38:22 -0700 (PDT)
Received: from pps.filterd (m0049462.ppops.net [127.0.0.1]) by m0049462.ppops.net-00191d01. (8.16.0.27/8.16.0.27) with SMTP id x6NGWPtg048952; Tue, 23 Jul 2019 12:38:19 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049462.ppops.net-00191d01. with ESMTP id 2tx5uh86p9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 23 Jul 2019 12:38:19 -0400
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 x6NGcHuv015957; Tue, 23 Jul 2019 12:38:18 -0400
Received: from zlp27130.vci.att.com (zlp27130.vci.att.com [135.66.87.38]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id x6NGcAsv015801 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 23 Jul 2019 12:38:10 -0400
Received: from zlp27130.vci.att.com (zlp27130.vci.att.com [127.0.0.1]) by zlp27130.vci.att.com (Service) with ESMTP id F19ED400B57D; Tue, 23 Jul 2019 16:38:09 +0000 (GMT)
Received: from MISOUT7MSGHUBAB.ITServices.sbc.com (unknown [130.9.129.146]) by zlp27130.vci.att.com (Service) with ESMTPS id DD56E400B57C; Tue, 23 Jul 2019 16:38:09 +0000 (GMT)
Received: from MISOUT7MSGUSRDB.ITServices.sbc.com ([169.254.2.174]) by MISOUT7MSGHUBAB.ITServices.sbc.com ([130.9.129.146]) with mapi id 14.03.0439.000; Tue, 23 Jul 2019 12:38:09 -0400
From: "DOLLY, MARTIN C" <md3135@att.com>
To: "3gpp-ietf-coord@ietf.org" <3gpp-ietf-coord@ietf.org>, "sdas@perspectalabs.com" <sdas@perspectalabs.com>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, "magnus.westerlund@ericsson.com" <magnus.westerlund@ericsson.com>
Thread-Topic: [tsvwg] [QCI-Diffserv] Side meeting at the IETF Montreal - call for agenda items
Thread-Index: AQHVQXUC/onlSZzieU2LL+icGcb9jQ==
Date: Tue, 23 Jul 2019 16:38:08 +0000
Message-ID: <8843EB53-9BF4-4163-950D-47F98032A65A@att.com>
References: <089A4A3D-7F87-4FCE-A690-102B0CAAB1F7@cisco.com>, <FE828F6E-64EF-4D35-883F-ED5041335011@cisco.com>
In-Reply-To: <FE828F6E-64EF-4D35-883F-ED5041335011@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_8843EB539BF44163950D47F98032A65Aattcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-23_07:, , 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=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1907230163
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/-6zNfUQ2hN5AlWK12MA-Nq9RsH8>
Subject: [3gpp-ietf-coord] Fwd: [tsvwg] [QCI-Diffserv] Side meeting at the IETF Montreal - call for agenda items
X-BeenThere: 3gpp-ietf-coord@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: 3GPP IETF COORDINATION <3gpp-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/3gpp-ietf-coord>, <mailto:3gpp-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/3gpp-ietf-coord/>
List-Post: <mailto:3gpp-ietf-coord@ietf.org>
List-Help: <mailto:3gpp-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord>, <mailto:3gpp-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jul 2019 16:38:25 -0000

Greetings

In light of yesterday’s agreements on a way forward, does this meeting make sense?

Thank you

Martin C. Dolly
Lead Member of Technical Staff
Government & Services Standards
AT&T
Cell: +1.609.903.3360<tel:+1.609.903.3360>
Email: md3135@att.com<mailto:md3135@att.com>

Begin forwarded message:

From: "Jerome Henry (jerhenry)" <jerhenry@cisco.com<mailto:jerhenry@cisco.com>>
Date: July 23, 2019 at 5:42:51 AM GMT-4
To: "tsvwg@ietf.org<mailto:tsvwg@ietf.org>" <tsvwg@ietf.org<mailto:tsvwg@ietf.org>>
Subject: Re: [tsvwg] [QCI-Diffserv] Side meeting at the IETF Montreal - call for agenda items

Dear all,
In order to allow to reduce session conflicts, we moved this meeting to Wednesday, 10:00 - 11:45, still in room C2 (21st floor).
I know it still conflict with other sessions of great interest, but this slot seems to be the one that offers least friction.

Looking forward to your input!

Jerome

On 7/2/19, 9:10 AM, "Jerome Henry (jerhenry)" <jerhenry@cisco.com<mailto:jerhenry@cisco.com>> wrote:

   Dear all,

   With the release of the meeting agenda we are now able to book side meetings.

    A number of people have contacted me about meeting in Montreal, and that they wouldn’t be available before Tuesday, but would want to meet before our tsvwg slot on Thursday.  Conveniently, Tuesday morning is reserved for side meetings.  I propose we take advantage of this from 8:30 - 9:45 (yes, this stops right on time for the 1st session) in room C2 (21st floor).

   In this meeting, we would discuss https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dhenry-2Dtsvwg-2Ddiffserv-2Dto-2Dqci_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=G9v8uCSSQhCmpw7ItG0r2g&m=6VupxqcNwlApz6fXbjud6T60EJkPhDbLRH13pIdyHHg&s=AKoeaeooP-uk9onbBdfZvkJebFkqY2opou2ReBSSU4s&e= and whether IETF should (or not) build recommendations for traffic traversing these two domains. Of course, this is what I think our current conversation is at, but please chime in if you would like to add to, or modify the agenda. Our ambition is to have a common understanding by the tsvwg Thursday slot.


   Jerome

   Ps: reminder: side meetings are not “official” anything.  Just a gathering of people with a common interest.  However, the meeting will run under the IPR rules of the IETF, regardless.  All are invited.

v2.23.0 | Report a Bug | By Email