Re: [rtcweb] rtcweb - Not having a session at IETF 102

Tim Hollebeek <tim.hollebeek@digicert.com> Thu, 31 May 2018 13:40 UTC

Return-Path: <tim.hollebeek@digicert.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DB3312EC57; Thu, 31 May 2018 06:40:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.599, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=digicert.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 olJS85NHcEFd; Thu, 31 May 2018 06:40:52 -0700 (PDT)
Received: from mail1.bemta8.messagelabs.com (mail1.bemta8.messagelabs.com [216.82.243.198]) (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 E25AB12F2AB; Thu, 31 May 2018 06:40:51 -0700 (PDT)
Received: from [216.82.241.100] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-6.bemta-8.messagelabs.com id BF/BD-28268-36BFF0B5; Thu, 31 May 2018 13:40:51 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA1WSa0hTYRjH9+6cHU/i6nVqe5LsspLCmmihqV3 UT0kRBhl0EfIsT260i+ysmvZBofIytcyKbKmzsgXWKEupLLvYummIiqYUUS4hKg3Nwrwk7exM q2+/5/n/+b/P8/LQhKyTCqZZs4k16hmtgvIlexc1+CtVE3N2R5w9CjHt556gmOLBXjLGMZXvk 0Akjf/sppJqasbEW8W7JBq9ymBOk6jzBholmUcSzZa8T0QuerHBgnxpEhcT4KwakfCFDJ8Qw8 ilQiQU7xC0llaRFjSLpnAEvG56LuY5EKdCT90NHwuiaQJHQfn7bXw7AMeDs3KIFCwJ8MxxmeQ tgTgOyit8+TaJQ+Gi84PHInWn/H5nl/AswzkwfPIUwfMsvA7yhyo9HoTnwmjLNc+rBJbDm36b hwEHQl9HKyVwEHz+OCUR/KlQOdLs7Svg1dtcUuAQ6LQVedYCXC+G1sEur0kJQ2fOEAI/QjDcI Rc4DK7Zq7ye/dD7cIyY7hc4rd4hFkBtSR8phDYRcN1SgARhPjS0XaIEoYSCoe5bpLBmOpyubf YKHxHcnSijStEK6z/rWd0agW0IHCfaJVbPP/nDy3P9pGBSQuODR4TAC+H2YIWX10L5+GNK4MV wuqjPR+Ao+Pp0GFUjuhYt51jjQdaojIwOVxk1GWqTjtFolZERMeE6luOYDFbLqLjwvQbdTeS+ rxyRCN1Bpfc2NqN5tFgRJP3WNme3bLbKkJ6lZjj1HuMBLcs1o/k0rQBp9rhb8zeyGax5n0brP tJpGWg/RaA0a8wtS7lMRsdpMgSpBSnpyfqyYkJG6g16Nlgu3cJnYN6kPqCfiZg+9U4UEhwgRS KRSOaXyRp1GtP/+hckp5EiQJrDp/hp9KaZl764hxC7hyjI8wxhYv5KwbmIPLT0amxyfe6xsi3 k5PqGlmObF6rOJ0F2rMF1y8aJ0lzLAkZ70rcfvGKY2ORrb4RPURdSCiHHdtgeNzd+wxr2e2LB cVfyj9V+Nnvdr/bulY2fx9f27t+088qSppMDKW1d0avw2P2yNife0b+jIkzuKkqodlkd8ZWx+ aHPrxclJSpITs1EhhFGjvkDcNnzduUDAAA=
X-Env-Sender: tim.hollebeek@digicert.com
X-Msg-Ref: server-10.tower-220.messagelabs.com!1527774049!197890431!1
X-Originating-IP: [216.32.181.17]
X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass
X-StarScan-Received:
X-StarScan-Version: 9.9.15; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32104 invoked from network); 31 May 2018 13:40:50 -0000
Received: from mail-co1nam03lp0017.outbound.protection.outlook.com (HELO NAM03-CO1-obe.outbound.protection.outlook.com) (216.32.181.17) by server-10.tower-220.messagelabs.com with AES256-SHA256 encrypted SMTP; 31 May 2018 13:40:50 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=digicert.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7ttye3kCnP5dxRzMaomXoJUWEIB59eHcVszMptP3ja8=; b=YL+MkzwPpYWp5gds8A4w6P/xFQE3Wlqi/XYoaoBJ+XqGqzOM8zeQtQxasDHPtJfpmR+JWJs6JdvE3Ec0rE0OZvOwRokHpMmMby5O3bcFX6MvcAvp913dpffDvmb3HVIVbcWmAw91YJN4NuEDNURjsoATGXCQ51UOslkAEHDp3Yo=
Received: from BN6PR14MB1106.namprd14.prod.outlook.com (10.173.161.15) by BN6PR14MB1396.namprd14.prod.outlook.com (10.172.150.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.797.11; Thu, 31 May 2018 13:40:47 +0000
Received: from BN6PR14MB1106.namprd14.prod.outlook.com ([fe80::4dfb:25a:be82:3618]) by BN6PR14MB1106.namprd14.prod.outlook.com ([fe80::4dfb:25a:be82:3618%3]) with mapi id 15.20.0820.010; Thu, 31 May 2018 13:40:47 +0000
From: Tim Hollebeek <tim.hollebeek@digicert.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
CC: "rtcweb-chairs@ietf.org" <rtcweb-chairs@ietf.org>
Thread-Topic: [rtcweb] rtcweb - Not having a session at IETF 102
Thread-Index: AQHT+Bi955vJ8JyMWkyn1RMHvtdmMaRJfb0AgABc91A=
Date: Thu, 31 May 2018 13:40:47 +0000
Message-ID: <BN6PR14MB110695818A575BF9D6787E5E83630@BN6PR14MB1106.namprd14.prod.outlook.com>
References: <152768631266.27594.10418369950986413860.idtracker@ietfa.amsl.com> <D7358987.30B13%christer.holmberg@ericsson.com>
In-Reply-To: <D7358987.30B13%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [173.71.184.143]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR14MB1396; 7:uG//ShkDVmkQICtDofHrje5jXVFkpILg16v+OyfQRgquEIPEYfO6GNCdcq+LbuyP45D5kvwRaVAr+nHx3+pbrojzb3XeW0L6Wa0cf8T0OB5PeWrVQBFtnCjhXTl1vJSaBDSgkHqOtXXtIkWjXq0y+zAVsIAFxgTDAoxPfcuV1P0q8iE648Q2vz/VTZWxYqquxbYJwo3ryeBLzGvPp49EcNE58fECPJOIGHMwkmxGRAeHHwGd1pYzBsccmkafsNwZ
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(49563074)(7193020); SRVR:BN6PR14MB1396;
x-ms-traffictypediagnostic: BN6PR14MB1396:
x-microsoft-antispam-prvs: <BN6PR14MB139679CEE973F126A79DDC3683630@BN6PR14MB1396.namprd14.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040522)(2401047)(5005006)(8121501046)(3231254)(944501410)(52105095)(10201501046)(3002001)(93006095)(93001095)(149027)(150027)(6041310)(20161123558120)(20161123562045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(6072148)(201708071742011)(7699016); SRVR:BN6PR14MB1396; BCL:0; PCL:0; RULEID:; SRVR:BN6PR14MB1396;
x-forefront-prvs: 06891E23FB
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39380400002)(366004)(39860400002)(376002)(346002)(189003)(199004)(13464003)(966005)(76176011)(5250100002)(7696005)(44832011)(97736004)(6436002)(14454004)(478600001)(229853002)(5660300001)(4326008)(53546011)(2501003)(6506007)(110136005)(476003)(59450400001)(99286004)(102836004)(486006)(3660700001)(86362001)(11346002)(446003)(2906002)(186003)(316002)(26005)(3280700002)(9686003)(6116002)(3846002)(6306002)(55016002)(33656002)(53936002)(6246003)(25786009)(105586002)(106356001)(68736007)(99936001)(7736002)(81166006)(66066001)(81156014)(8676002)(8936002)(2900100001)(305945005)(74316002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR14MB1396; H:BN6PR14MB1106.namprd14.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: digicert.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: b1mvCLuYJSw2XlcuhhQ31IAZyxtwOEC/k8iXWVp6MvtV5NOhSXZKt/xiA3V6Pfh9naH/d3TqCpO8zd3N/hgl29zPEXwMw1IhbliRJ6MGykJkCYmhPzPCCt3ElonCc+dhPHUQ6I7TJmRCYEeS8deJPKYl0+m719RDqIh0929Bs+syLWFyYxqqAteTb0pNWNy6
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="2.16.840.1.101.3.4.2.1"; boundary="----=_NextPart_000_0723_01D3F8C3.F0802F00"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: bd2f94d8-2443-4bbe-8e49-08d5c6fc1dbb
X-OriginatorOrg: digicert.com
X-MS-Exchange-CrossTenant-Network-Message-Id: bd2f94d8-2443-4bbe-8e49-08d5c6fc1dbb
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 May 2018 13:40:47.4432 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf813fa1-bde5-4e75-9479-f6aaa8b1f284
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR14MB1396
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/zXsdrzIoljjGQL_thACF3SKHOG0>
Subject: Re: [rtcweb] rtcweb - Not having a session at IETF 102
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 13:41:02 -0000

I agree.

-Tim

> -----Original Message-----
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Christer
> Holmberg
> Sent: Thursday, May 31, 2018 4:11 AM
> To: rtcweb@ietf.org
> Cc: rtcweb-chairs@ietf.org
> Subject: Re: [rtcweb] rtcweb - Not having a session at IETF 102
> 
> Hi,
> 
> I think we need to have discussions (in SOME forum) about the Identity
> attribute. Because, in addition to the things that need to be clarified,
based on
> the comments it seem like there are opinions/understandings that
contradict
> what is currently written in the draft.
> 
> Regards,
> 
> Christer
> 
> 
> On 30/05/18 16:18, "rtcweb on behalf of IETF Meeting Session Request Tool"
> <rtcweb-bounces@ietf.org on behalf of session-request@ietf.org> wrote:
> 
> >
> >
> >Sean Turner, a chair of the rtcweb working group, indicated that the
> >rtcweb working group does not plan to hold a session at IETF 102.
> >
> >This message was generated and sent by the IETF Meeting Session Request
> >Tool.
> >
> >
> >_______________________________________________
> >rtcweb mailing list
> >rtcweb@ietf.org
> >https://www.ietf.org/mailman/listinfo/rtcweb
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb