Re: [rmcat] Magnus Westerlund's No Objection on draft-ietf-rmcat-nada-12: (with COMMENT)

"Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com> Fri, 06 September 2019 16:41 UTC

Return-Path: <xiaoqzhu@cisco.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EC16120967; Fri, 6 Sep 2019 09:41:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=P4bSqkJZ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=sNMYKOO4
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 1kstoBMZZOmc; Fri, 6 Sep 2019 09:41:33 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 295751208D9; Fri, 6 Sep 2019 09:41:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3294; q=dns/txt; s=iport; t=1567788087; x=1568997687; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Sm8sCHk6msu8lpwDqCOuFDV21LL4/JOzZjcLrs3Djww=; b=P4bSqkJZUdSjiDfR8OHbAipxRnQ1cbpmuOjUSprbzAk2K4rMwm4WeKhA x+yCF/yPzXRVDS7EepKsHwBurdBNcJ1fUoVc8r2D5pDoOYdZfmT9ZkEVi P4zzviEhaaDi+jdStBQFZgRpDDAJSi5bMcOGZBqFqOkT09dD83obK88tn M=;
IronPort-PHdr: 9a23:sO+YKxbPULthbkJbkezTnpT/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el20gabRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn1NksAKh0olCc+BB1f8Kav6biU9BdZCSXdu/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DcAACyi3Jd/40NJK1lHAEBAQQBAQcEAQGBVQUBAQsBgURQA21WIAQLKoQhg0cDinOCN5gSgS4UgRADVAkBAQEMAQEjCgIBAYQ/AheCICM2Bw4CAwkBAQQBAQECAQYEbYUuDIVLAgEDEhERDAEBNwEPAgEIGgImAgICMBUQAgQBDQUbB4MAAYFqAx0BDp4LAoE4iGFzgTKCfQEBBYE2Ag5BgwkYghYDBoEMKAGLdxiBQD+BEScME4JMPoJhAQEBAgGBKgESAYMqMoImjFuCYJwaaAqCIIZ9iXmDexuCNIc8jwuNfYgAkGQCBAIEBQIOAQEFgVkELWdYEQhwFWUBgkGCQjiDOoUUhT9zAYEojQWCRQEB
X-IronPort-AV: E=Sophos;i="5.64,473,1559520000"; d="scan'208";a="321211489"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 06 Sep 2019 16:41:26 +0000
Received: from XCH-ALN-013.cisco.com (xch-aln-013.cisco.com [173.36.7.23]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x86GfQpQ020487 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 6 Sep 2019 16:41:26 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-013.cisco.com (173.36.7.23) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 6 Sep 2019 11:41:25 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 6 Sep 2019 11:41:24 -0500
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 6 Sep 2019 11:41:24 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZV/nWpJtUvjz2m8kIWvjNEAQ+90TDvtO0CJ3B1h9VED2+xEk8HqciYXeXPidAYQ1HzrTR969MqCHXoBnsNL+PMfAnvajUPB6Dspl6DNmBs6AF1Zpto3BIS4MvUq9EkewYd4nRH1WYBUlVDN+3r2m56fe6NU9D9L6466KzYMaTZNqZzcVe88v+n0gBxGnjpZsTuWql8R2q90eLJDcVqmYGrk60NnHUj7ghdpnYIp6OK6nZNutUXhnBAXJzALdOJYEfWPpDF+yU6cb8XJLhYxjKa5F3mq9JJOu3UYG0Do02QkI/rrc0vicX0BQEXg/dPcNeStqzWDlC/ULpPLjtmR23A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Sm8sCHk6msu8lpwDqCOuFDV21LL4/JOzZjcLrs3Djww=; b=SZ6YjtiXKqYqdpZweSwW+Iou4LKWmJOPDxUeo9Hrj6nu6sTrU3ToJ93p3R+Wbj2aHTasRcjP2iEYJwNStrkWSS7fZn+skLmc4WULmMafUFw50I9xDiuKQ124Q2yNXhgsqFFkQhbtRDQO4SK8wJO2W4m84F4DHVQwgi/fpGpQ7TIISTXnJUThD+dwl+Fsd8q15Kv8PghpKa3RbOh/RUCeDDE7kNfSNArSels8koyZqlt2JeitDEtWsKCYDSPyTlxM/JWtVmTVn6nrhYn+dSLDYwk0HFEL6UCnFVDuoEdk8ZAf6Yn9SN54fT9nUb9AJaQ7NS457KTYMcgDpighj6dg1w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Sm8sCHk6msu8lpwDqCOuFDV21LL4/JOzZjcLrs3Djww=; b=sNMYKOO4SuVr3NWm4WS2aXSmgETKZDe8kUNgRnhcHzf4ku4mjXYnSufKNdjLMRH0whARQY1LczGuZUNUyJNxsq0iGjdGQx7rTeCnV0G8aLRyFOnIeHPIciBw83+c0/N8k6+egdU2KpmjI5Byv4zINj4/muKpKWPH7LGTEBvwocQ=
Received: from CY4PR11MB1559.namprd11.prod.outlook.com (10.172.72.140) by CY4PR11MB1303.namprd11.prod.outlook.com (10.169.254.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2241.14; Fri, 6 Sep 2019 16:41:23 +0000
Received: from CY4PR11MB1559.namprd11.prod.outlook.com ([fe80::53:33f3:ea63:7f72]) by CY4PR11MB1559.namprd11.prod.outlook.com ([fe80::53:33f3:ea63:7f72%3]) with mapi id 15.20.2199.027; Fri, 6 Sep 2019 16:41:23 +0000
From: "Xiaoqing Zhu (xiaoqzhu)" <xiaoqzhu@cisco.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-rmcat-nada@ietf.org" <draft-ietf-rmcat-nada@ietf.org>, Martin Stiemerling <mls.ietf@gmail.com>, "rmcat-chairs@ietf.org" <rmcat-chairs@ietf.org>, "rmcat@ietf.org" <rmcat@ietf.org>
Thread-Topic: Magnus Westerlund's No Objection on draft-ietf-rmcat-nada-12: (with COMMENT)
Thread-Index: AQHVY/H+fAl/b7IjkkWu9wPquGHAH6ceiB8A
Date: Fri, 06 Sep 2019 16:41:23 +0000
Message-ID: <97979243-F28C-42FA-8C66-51AC2970170F@cisco.com>
References: <156769186904.22703.13173070160088210141.idtracker@ietfa.amsl.com>
In-Reply-To: <156769186904.22703.13173070160088210141.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1c.0.190812
authentication-results: spf=none (sender IP is ) smtp.mailfrom=xiaoqzhu@cisco.com;
x-originating-ip: [2001:420:1402:1250:3d62:80e8:fc02:e64c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 3c900a0e-2c68-479d-910d-08d732e90dc8
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:CY4PR11MB1303;
x-ms-traffictypediagnostic: CY4PR11MB1303:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <CY4PR11MB1303719AE77939BE43FF5DA1C9BA0@CY4PR11MB1303.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0152EBA40F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(376002)(366004)(39860400002)(346002)(136003)(189003)(199004)(46003)(476003)(102836004)(186003)(76176011)(446003)(71190400001)(110136005)(58126008)(486006)(256004)(2616005)(33656002)(11346002)(316002)(54906003)(71200400001)(36756003)(99286004)(5660300002)(25786009)(6506007)(6246003)(53936002)(86362001)(64756008)(66556008)(6512007)(66946007)(66476007)(66446008)(6116002)(7736002)(966005)(8676002)(6436002)(2906002)(91956017)(4326008)(305945005)(76116006)(6306002)(81156014)(478600001)(81166006)(8936002)(229853002)(6486002)(14454004); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR11MB1303; H:CY4PR11MB1559.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: xQEEAQEVGwSs15mCmpTVKjQXAJByO5VbEq3vGn1feUliJCnjRmv1WzDUF67BfyDGsNDrEU/mlCCaR86hj9ueN/t8pgnQhMTpSRdzb/qylXcK013HbwaPPijE1HRNbnQDaDYv4UDSB7jMtEqZE7ZvO9GAk+cswEtxxFLIhJr2Uqdk5xGXEnmnGjOVW+IGwS4+45pj88FO5gfIy9pfvstKza41F+kcQ1GveSd9aBJyAyjIWQtLeSltH5J7Cfk78B8urXtweGxEAQgIv+9QQ7z4hlLYt6rZq2dVPlQ1HH/ui8hnC1HdUgo4ESsPJSKFr7ypaGhNW7zbINsnJReotN7StOkUfy1wTn6LW35Ul0kBYjkptoCqGyi8b7spHvsWWC0bcPyK6nywKYzyjMcZtuL4u0PeWtExsswMyFf2mrGXc2I=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <4731F720D18DF047915A79259C7CC2DA@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3c900a0e-2c68-479d-910d-08d732e90dc8
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Sep 2019 16:41:23.5571 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ZjnmYR56CNhVvoAWM212pXuTQv+m0VmblYIVluGwGw+iI86OmUS4f6v7S47qnN69zxl2krqBnk3yKNYlFzzECQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR11MB1303
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.23, xch-aln-013.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/zGXrxJUBNL6PWYfsLP2Sr_IUM5E>
Subject: Re: [rmcat] Magnus Westerlund's No Objection on draft-ietf-rmcat-nada-12: (with COMMENT)
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Sep 2019 16:41:36 -0000

Hi Magnus, 

Thanks for your review of this draft. 

Regarding your question on transmission timestamping mechanism in Section 5.1.1.: our current implementation
haven't yet considered the Transmission Time offset in header extension, but rather simply generated a timestamp
via local system clock and embedded that information in the transport packet header. 

We've revised the description accordingly, to more accurately describe what the current implementation does and
the potential solution via a standardized format: 

https://tools.ietf.org/html/draft-ietf-rmcat-nada-13 , in Sec. 5.1.1:

	... For experimental implementations, instead of relying on
   	RTP timestamps and the transmission time offset RTP header extension
   	[RFC5450], the NADA sender can generate its own timestamp based on
   	local system clock and embed that information in the transport packet
   	header.  

Best regards,
Xiaoqing
 

On 9/5/19, 8:58 AM, "Magnus Westerlund via Datatracker" <noreply@ietf.org> wrote:

    Magnus Westerlund has entered the following ballot position for
    draft-ietf-rmcat-nada-12: No Objection
    
    When responding, please keep the subject line intact and reply to all
    email addresses included in the To and CC lines. (Feel free to cut this
    introductory paragraph, however.)
    
    
    Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
    for more information about IESG DISCUSS and COMMENT positions.
    
    
    The document, along with other ballot positions, can be found here:
    https://datatracker.ietf.org/doc/draft-ietf-rmcat-nada/
    
    
    
    ----------------------------------------------------------------------
    COMMENT:
    ----------------------------------------------------------------------
    
    A Question regarding Section 5.1.1.
    
    This section recommends using a NADA specific transmission timestamping
    mechanism embedded in the transport. What about the header extension for       
    Transmission Time offsets? Are there a reason to not discuss using that a
    potential solution for providing that. I know it has the downside of being
    expressed in RTP payload format timescales and not in a nice and likely more
    compact milisecond, but it is a standardized solution that can provide the
    necessary signal.