Re: [MMUSIC] Signaling Additional SRTP Context information via SDP - draft-davis-mmusic-srtp-assurance
"Kyzer Davis (kydavis)" <kydavis@cisco.com> Thu, 12 October 2023 15:02 UTC
Return-Path: <kydavis@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1B38C1705EC for <mmusic@ietfa.amsl.com>; Thu, 12 Oct 2023 08:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.604
X-Spam-Level:
X-Spam-Status: No, score=-9.604 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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="Ku5jTS52"; dkim=pass (1024-bit key) header.d=cisco.com header.b="GOILwfIP"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1DMcd92obKWj for <mmusic@ietfa.amsl.com>; Thu, 12 Oct 2023 08:02:02 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (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 ACBDAC151985 for <mmusic@ietf.org>; Thu, 12 Oct 2023 08:02:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17014; q=dns/txt; s=iport; t=1697122922; x=1698332522; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=0kPF3RUmI+g3dqNjIp79J4gz7YlGkWSoaalO+AEo2RY=; b=Ku5jTS528Kk+t3GQFLXHCtIOBmG9MC8e8lfoAFlneELPd9BuLgCP//D/ w3OYBWTNNk9IezR62rKq/ymX2ulvDpWceo/txk+RdJ7gehncZTcwUWrPz CXhG/ZNu6EssCZ6e8a4jd6f+JY4TamFW214FT08+DPWJVJPQXbKWjlLdP 8=;
X-CSE-ConnectionGUID: jwPSvsiNSCSPXXXcHecV1A==
X-CSE-MsgGUID: r22/uN5USnG3es1T6qJZgA==
X-Files: smime.p7s : 5465
X-IPAS-Result: A0ADAAC7CChlmIUNJK1aGgEBAQEBAQEBAQEDAQEBARIBAQEBAgIBAQEBZYEWBQEBAQELAYFlUngCKy4TFxJIA4RPg0wDhE5fiGMDnXsUgREDVggHAQEBCgMBATQQBAEBhQcChxACJjQJDgECAgIBAQEBAwIDAQEBAQEBAQIBAQUBAQECAQcEFAEBAQEBAQEBHhkFDhAnhWgNhkwBAQEBAgESER0BATcBBAcEAgEGAhEDAQEBFhIDAgICMBQJCAEBBAENBQgGDQeCXAGCFiUSEQMBEAaXbY9NAYFAAoooeoEygQGCCQEBBgQFgTwCAg4DDy+wVgcDBoFIAYFWhhkaAWhogmGBCIMugR8nG4FJRIEVQ4I3MT6CPyIBAQEBARd/EgESAQccFQkfgxw5gi+Df4IrgxAHMoIkg1mBFIIAcoJXhARvE0dwGwMHA4EDECsHBC8bBwYJFi0lBlEELSQJExI+BIFngVEKgQY/Dw4RgkMrNjYZS4JbCRVBBEl2ECsEFBeBEwRqBRoVHjcREhcNAwh2HQIRIzwDBQMENAoVDQshBRRDA0cGTAsDAhwFAwMEgTYFDx4CEBoGDikDAxlNAhAUAzsDAwYDCzEDMFdLDFkDbyE2A0QdQAMLaAUOAi01Bg4bBQRkWQWZQ4IRPDE1gUEBEBVMKz0NCxcUDgIgAgc9FR0tGgobIwUGAQcBLRKFcow9EINmi0uhKIE3CoQMhk6DKYIKlT0XhAGeTIY3Ypg6IIIvixSVI4UeAgQCBAUCDgEBBoFjOiILHCJwcBUagwgTPxkPjiAMDQkWgiKBHoUUimV2AgEFBS4CBwEKAQEDCYtKAQE
IronPort-PHdr: A9a23:Le+tNBylG0b3YnfXCzMSngc9DxPP853uNQITr50/hK0LKOKo/o/pO wrU4vA+xFPKXICO8/tfkKKWqKHvX2Uc/IyM+G4Pap1CVhIJyI0WkgUsDdTDCBjTJ//xZCt8F 8NHBxd+53/uCUFOA47lYkHK5Hi77DocABL6YAlkKu3rG5X6hMWs3Of08JrWME1EgTOnauZqJ Q6t5UXJ49ALiJFrLLowzBaBrnpTLuJRw24pbV7GlBfn7cD295lmmxk=
IronPort-Data: A9a23:iCsWCa2uRpWg1mx+fPbD5Xhxkn2cJEfYwER7XKvMYbSIpGtil2len TNbADbYJb/RMSHyZpovP9PnsQ9E7KZh/KYgFVsx+Dd1EGkiRaHtX9rIf02pbijPdpyZExM94 pxBZIPNIc1tRyGDrU/9PLGw8yhw2/GEH+CmBbebZ3orGwM/Eit7hE84xrA03NNk3rBVb+/jV fba+6Uzb3f4h2ApWo5t15++lf9PgBjTkD0U51I0P/oXtwaExyEcV58UK626IiP2G4NfFeTnG 7fI5bzopWmxEzXBpT+GfhcXVmVQH9Y+6CDX0iI+t5CK20UE/mpqlP9jaJLwUG8P4x2Rhdd91 d5RgpK5TAYtL8Xklf8UO/ViO3kW0ZZupvmfehBTjeTJlxedKiO1ma00ZK0LFdRwFthfUDkmG cMwcFjhXjjb78qqzbSyTPVbh8hLBKEH66tG5xmMZRmAZRoXacirr5fivLe07x9s7ix6JssyU uJCAdZZgLssVDUUUrsfIMpWcO5FHRATeRUAwL6ejfJfD2Q+UGWd3ZC1WOc5dOBmSu1XgX6ju HnH2V/SOSkqBOyU6TeOzCuF07qncSPTAOr+FZWx8vpsxVaU3GFWUURQXlqgqv7/gUm7Mz5dA xVLoWx18+5rrwryFYKVsx6Q+BZoujYfStZZDewhwAqM0aHTpQ2eAwDoSxYYMoB6659vHmBCO lmhhYmzQiFJ7YCuT13G+6zNkW2rGxoaBDpXDcMDZVJVv4a8yG0ptTrKS8t4EaWdj9DpF3f32 T/ikcQlr7wXichO3KKh8BWe2nSnp4PCSUg+4QC/sn+ZAh1RZpGdXJKz6H7gxs14HLapRXmMt 0Zdsp3LhAwRNq2lmCuISeQLObim4feZLTHR6WKD+bF8p1xBHFb+IuhtDCFCyFRBaZ1dJWKwC KPHkUYAu8cNbSrCgbpfPtrZNig88UT3+T0JvNj4Y9xSZZ4ZmOSvo380PBb4M4wAbCERfUwXM JOfd4OnCmwXTP0+ijG3XOwal7Qsw0jSJF8/p7illHxLMpLHOxZ5rIvp1nPVPojVC4vf8G3oH y53bZfi9vmmeLSWjtPr2YASN0sWCnMwGIr7rcdaHsbafFs5QD1wU6OJne1wE2CAo0izvrqZl p1achEAoGcTeVWcQel3Qik5Mei2DcoXQYwTZHB3Zj5EJETPka72vPtAKPPbjJEs9fdoyrZvX uIZdsCbasmjuRyZkwnxmaLV9dQ4HDzy3FrmF3P8PFAXIcU6LySXoYCMQ+ca3HRUZsZBnZFg8 +TIO8KyacdrejmO++6PNqzwkg7g4yRA8A+wNmORSuRulIzX2NECAwT6j+Q8JIcHLhCr+9dQ/ 1/+7cswzQUVn7IIzQ==
IronPort-HdrOrdr: A9a23:FpJxW6vP3sKWXANneRHxmPFu7skCOYAji2hC6mlwRA09TyXGrb HMoB1L73/JYWgqOU3IwerwSZVoIUmxyXZ0ibNhRItKLzOWyFdATbsSorcKpgeQeREWmdQtqJ uIH5IOb+EYSGIK8/oSgzPIXerIouP3jJxA7N22pxwCPGQaD52IrT0JdTpzeXcGPDWucKBJbq Z0kfA33AZIF05nCPiTNz0uZcSGjdvNk57tfB4BADAayCTmt1mVwY+/OSK1mjMFXR1y4ZpKyw X4egrCiZmLgrWe8FvxxmXT55NZlJ/K0d1YHvGBjcATN3HFlhuoTJ4JYczDgBkF5MWUrHo6mt jFpBkte+5p7WnKQ22zqRzxnyH9zTcV7WP4w1PwuwqhnSW5fkN5NyNyv/McTvLr0TtmgDi66t MM44utjesTMfoHplWl2zGHbWAzqqP+mwtQrQdatQ0sbWJZUs4RkWTal3klSqvp20nBmdsaOf grA8fG6PlMd1SGK3jfo2l02dSpGm8+BxGcXyE5y4aoOhVt7ThEJnEjtYcit2ZF8Ih4R4hP5u zCPKgtnLZSTtUOZaY4AOsaW8O4BmHEXBqJaQupUBjaPbBCP2iIp4/84b0z6u3vcJsUzIEqkJ CEVF9Dr2Y9d0/nFMXL1pxW9RLGRnm7QF3Wu4xjzok8vqe5SKvgMCWFRlxrm8y8o+8HCsmeQP q3MII+OY6rEYIvI/c+4+TTYegkFZBFarxhhj8SYSP7nv72
X-Talos-CUID: 9a23:H55YamwxeZC3uxpnkZeXBgUWBfgebGbc6kz7GHeIOVZiaLCedwa5rfY=
X-Talos-MUID: 9a23:YH4M+AofljQHg2h1qroezys4boB1xfmTM0Yiypgd4vXaLA5CNB7I2Q==
X-IronPort-Anti-Spam-Filtered: true
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-3.cisco.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Oct 2023 15:02:01 +0000
Received: from rcdn-opgw-2.cisco.com (rcdn-opgw-2.cisco.com [72.163.7.163]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id 39CF20of002419 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for <mmusic@ietf.org>; Thu, 12 Oct 2023 15:02:01 GMT
X-CSE-ConnectionGUID: czL0LdqURb6YG1gS3nDDWw==
X-CSE-MsgGUID: 2fZ9/finRwKpd11b3QJybA==
Authentication-Results: rcdn-opgw-2.cisco.com; dkim=pass (signature verified) header.i=@cisco.com; spf=Pass smtp.mailfrom=kydavis@cisco.com; dmarc=pass (p=quarantine dis=none) d=cisco.com
X-IronPort-AV: E=Sophos;i="6.03,219,1694736000"; d="p7s'?scan'208";a="4645903"
Received: from mail-dm6nam11lp2169.outbound.protection.outlook.com (HELO NAM11-DM6-obe.outbound.protection.outlook.com) ([104.47.57.169]) by rcdn-opgw-2.cisco.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Oct 2023 15:02:00 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=FFMjxcK2y3ECW1BgMbKcpzVUUL4VFzskcl0PzOJZ5FfV0Tm5hTrULKekfszWtCW6F9X6+ix1VkgEDHAt0Q/WhCGB8pAFKGtXnt9S6uBabGX1Aoaf8BaExouxIJFZPx89FtGqePQW43M/uyF7qw+Fg5VhaUXY+cvAAFk92WQDkhp/lgSpzDQYOG9k/g5uSBtYFRIy3eCmhve+UxmeNgGZrJZZLwzHTLRCteSF+OJJ2RYtI7hZ5HI3x5ohdxU63KQmP7vLZwBEVNcQ6sHdwUDlUJcG6bOLgRVuV8Ov3LAef13U0g8WCBOdR321ES9JJ5ryu5Myc7bI+m3NMMmorsMbqg==
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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=34I5FBTfzOZSZRd854NFf+Fnjz6NjRtdwwI2xVhjTD4=; b=n2vyK/QrZNotrnzB+74UGM+SzlJfVhniMqUHW3Ab3x9kX/eKq6j2xyGgcjIYJCXSQbrVJ1ttYEP5GPflkCY2x6INTLP6gNto5Po4NxIJlUm90RjABNftYRJwkXYfwnkNt49JaGIRhlqS4k1tSacV53Rajvya54ymLLUvDA4L4FSzYa9XmcWx9wBmI/oSsm011iiplfUo5NsFiIcuAUj8GeZbh7lx3JP1RruMSBfVImF59sOYtr+KjU7aTLR3ljE4vkHAd5qhaImc1KIG7wqdIAexoMOXx3InupmN1hnm2/uihZ+Y6HAyDZAd7GMOxeGm95kGzK0bqEDUgWynHjRVbw==
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.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=34I5FBTfzOZSZRd854NFf+Fnjz6NjRtdwwI2xVhjTD4=; b=GOILwfIPkXyp6Ukj3xQccbO0MJfOtyoAtoEycIfvIDpCN7sb9byd7lajVsZJEC6FMNRYw7zYTsQNI9/XXww/3sAlLiiHuCW9zFPyVOzUaf/W39LCWnUND6x7tWgJUYAaKtd1WjFUuern8rmGlJqw4GFjgyxzJkpHMoLXkU11iLs=
Received: from PH0PR11MB5029.namprd11.prod.outlook.com (2603:10b6:510:30::15) by PH0PR11MB5175.namprd11.prod.outlook.com (2603:10b6:510:3d::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6863.40; Thu, 12 Oct 2023 15:01:55 +0000
Received: from PH0PR11MB5029.namprd11.prod.outlook.com ([fe80::ef5:68e2:bc47:eeee]) by PH0PR11MB5029.namprd11.prod.outlook.com ([fe80::ef5:68e2:bc47:eeee%6]) with mapi id 15.20.6863.040; Thu, 12 Oct 2023 15:01:55 +0000
From: "Kyzer Davis (kydavis)" <kydavis@cisco.com>
To: Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
CC: "Esteban Valverde (jovalver)" <jovalver@cisco.com>
Thread-Topic: Signaling Additional SRTP Context information via SDP - draft-davis-mmusic-srtp-assurance
Thread-Index: AdnLnxa1oeUTBHs9SrOCZ4d9gnl/4AvUikQQACOy1sAAAkWlgABVSEmgAA+T+lA=
Date: Thu, 12 Oct 2023 15:01:55 +0000
Message-ID: <PH0PR11MB50293C206BA914CBD36F4BD2BBD3A@PH0PR11MB5029.namprd11.prod.outlook.com>
References: <PH0PR11MB5029B53E9DF50EC1B420AF1EBB13A@PH0PR11MB5029.namprd11.prod.outlook.com> <PH0PR11MB5029896E1D6202953341CB27BBCEA@PH0PR11MB5029.namprd11.prod.outlook.com> <HE1PR07MB44410065064B77A55A8493C993CDA@HE1PR07MB4441.eurprd07.prod.outlook.com> <PH0PR11MB5029236B1114DE35C53A2BB2BBCDA@PH0PR11MB5029.namprd11.prod.outlook.com> <HE1PR07MB4441EE08225D3CE1C02BDDBA93D3A@HE1PR07MB4441.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB4441EE08225D3CE1C02BDDBA93D3A@HE1PR07MB4441.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: PH0PR11MB5029:EE_|PH0PR11MB5175:EE_
x-ms-office365-filtering-correlation-id: 2c95c307-3c92-49f0-7df8-08dbcb342d21
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: TY6H5mvMLonNkaFHUQ2KLCE/n5i3E55PcNdSbRT4eZccjP7QbhlnirVgOZqEQ4iVSTC1+DdYHtyGz8UPMivK1oRDnyZwUXLgGJB43uCpmgb1QZ9L6103hl57QKOrpaOXUfb372UbyeeSAEpHir5t8gXwnl6P98QxQsP1hp3eSkU7TN72Dwe+ErBjQeEkh05cLUd4ov0Myrptq9RSV5ueogRehsEE44OOBDmITvpWMtl7U2FKFLvrKt+7RXSiAmx9SjnlA2RpuBdpru/GsKSPuBVQi/aCf/+k7M80ZgV20UYB2jHukLvhmGA9YiUMpL+QCuQ2xCFWOpgxiKHgALLIfxVnhOwLFSA/SXm0/ev//Rfww1jzNwsLxMIYodAGYsd0d6jEg/45wheSdaDgaQrE3yt73QPRgJPtHGtMUML3A/wvNo/1E695+UM+RLPsFo7hbawGnSz/GqTE3H43u7Tkeca4gFmhzdVCn5QFrYGUVt1uyfc7PGckAH0DVXS41Gpvxe+NsFLYZ+PQSxLyhxfMxzsoaTrArBtZVbYIvlSlGGfsgofz8F48NJ0OjddHqjATejPrTQ+2LRy3l+7sIDnq2HXcYjMaAfhexPLx8nXas4+eLWngnLtEepS6ZGHV5wBummE2vPF4BhRBzkVhAPiZ4g==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:PH0PR11MB5029.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230031)(39860400002)(346002)(136003)(376002)(366004)(396003)(230922051799003)(1800799009)(64100799003)(186009)(451199024)(122000001)(66899024)(38100700002)(316002)(83380400001)(55016003)(66446008)(26005)(5660300002)(9686003)(33656002)(107886003)(99936003)(4326008)(86362001)(8936002)(66556008)(110136005)(41300700001)(66946007)(71200400001)(64756008)(76116006)(478600001)(7696005)(53546011)(6506007)(966005)(52536014)(2906002)(38070700005)(8676002)(66476007); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: YONgRxk5GzS0aTh/jyq8aJi1dSbbSzHqTIBeoJpKseofQaEtHOQBt7FBT3gTKtVuABq9ysgBLvKj3z0h4i4VnBGqexncO4mtmMaFNUukksTUKSQXTpQyJRp76zNGTceq7x2wf9SqXFnYpwKJcBfnLKoLZstp0ezQF2jqhGFB7JmhaKlyB7M+UjhJBTfnLXzoC00dqMTCAbyDYH9VQPrisdfT+Y6/wykx/c4QYc+rCuXuF0UExqhz12gp8CmfivvcNp17O6/IXotSTG7u0dc2YWoRDjlHJRw6kTwC93mNwavAU6BPiHLNl9dSQoOY8wldLmdzPaC5DirZD3Nx+J0rpF/hJW/Am0fS/EBtOIHAMKv0/eEhxbWihMUqR1zDseFO/QLQvfckDQbZmNfxEslO0hUAFZgmzKsPktf/s5CLb0blCaqjt4iZpSmXXdtm/Fww4/7oVTPpadSgEeRCj8+c0sLhBBHbgD2bTjnCkZv9Utr5YQyVAxbOm/URrV+0PZDQzHInNzuZDWrkoYE+sC4wVhxlyvXk5auXTkL64ke0eOe9FqLfZT1jKEpxlWRIH+hWnF7dNsGOSAZrVHKtulA2F25bPzc6mvcvereqOXoFBX3dAW5tP96YVHuzKj26DMtWvtVa2kXO8dE5J7YmWcRsU+sHVbkZvMg5PZnz7PjPdZka2TbnCdhhvtPvHGcJbd86QOlKI+Uh8KZUSxqPBZbM2np5xOlhOZnqkKPrtRHnGXN5B+ET4NLXyJHXr7Ryqz3dvi4Tj/aag9JxgJeWFaGNZy3vAvQVe3pdzHixMpgX44ayxJYBJ3YDQGecLT/S96g8fbDLzkeJHufrqbJ9BDnUp7bfPQtQAZd90Ue+x5UHXs2vlDwpinUvsvU6pDBvETxzWC37FltuIV0PhmywzIvejUBVozBSCP4J44Sol/fZ1r/IjLkt/jd5cO4BPRpr8iPvNaMN376KqlpSBXE/dT6Nik05B4NaGJqePlQwwlKwFvWc/IbiNP+NFfXT9pyEYT8K+nfRxZiFpnwWpVeEnZnDTw+hnwUUgtLZ8LZBGMHOerL8G4IzQ5Fes36pMLdHIMPb4MbixWEwOzbqOB5wuBP9WeF/uYiPaEqzWdaviwCik+cQTRsrLjOcmDZNtKMmMR4jPv4xFnXnqISe0ktpPfJkLwM9ZNIt1VCFelcTgTW5pMTHCmglTPccfd3UsmsQUYDVr+aCy5ioy06Vlar4CK174mm7l1CVqtzn0RONOEVJhaW7OLYOZFYEJiCfwWP6p6tdk+17uNV6CNEg99hxoF6umcCjJepWQwRT2ff2tjnKDkGGu6pjAXQWSTsCx6uw/t/XbrzvFddEY+TYHME5vycZiUI5lkXc97BhXo48kxGh32STxfrkYuULlGe+/vGDnaazZfgPkUlWz5TYtx7nKgrfySE9AOPZb+7c1gPFVJQiGalP6UrJ6KZZV9OB8KUjqNz8xXV/2599eTiIvIgCcQ7vp5OFmuqpasFcY8SNyi8kaLlZxZ1ILrRcZtFHAf2UIavQiJkVmgTFEQH7Hm7ZzggfuOKdedbACaMju1Bd4VicImY=
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_0004_01D9FCFB.8106FD10"
MIME-Version: 1.0
X-OriginatorOrg: cisco.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PH0PR11MB5029.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 2c95c307-3c92-49f0-7df8-08dbcb342d21
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Oct 2023 15:01:55.8436 (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: M3/PNSX1N5fJapmz/MsTQD2xE2KV+MnVYMHK7eIamNkF8iO53nf+/jcAtCwO43AkeSwFJkOCy0lxrqZ9Ke4YUg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH0PR11MB5175
X-Outbound-SMTP-Client: 72.163.7.163, rcdn-opgw-2.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/43TKFaRkJtUfUIVK2ATwA83br4I>
Subject: Re: [MMUSIC] Signaling Additional SRTP Context information via SDP - draft-davis-mmusic-srtp-assurance
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Oct 2023 15:02:07 -0000
> Would you not achieve the same thing by sending a new attribute without the value that has become unknown? Possibly, I cited a few things that come to mind over in the second command as I expanded upon the example below: https://github.com/kyzer-davis/srtp-assurance-rfc-draft/issues/18#issuecomment-1756076224 Re-posting that comment to this thread: Scenario that comes to mind: - Sent "ssrc=0xABCD" - Something occurs, lost track of SSRC (application failover or something without any shared context info.) - Send "ssrc=unknown" to state that they should fallback to the default application logics. This makes it nice to handle scenarios in programs where simply omitting a value that was signaled before could cause problems. For example in bullet 3 if one sent nothing; how would the other side handle it? This method is a graceful yet explicit callout that this value is now unknown. That being said, in the scenario above all 3 (or more values) are likely unknown and thus the following line comes into play: > Applications SHOULD NOT include SRTP Context attribute if all three values are unknown or would be omitted. For example, starting a new sending session instantiation or for advertising potential cryptographic attributes that are part of a new offer. If we drop "unknown" we would need text to state how to handle a value that was advertised before and then was removed later or relax the text above for all unknown to account for this later-in-session "all unknown" scenario. Thanks, -----Original Message----- From: Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org> Sent: Thursday, October 12, 2023 3:45 AM To: Kyzer Davis (kydavis) <kydavis@cisco.com>; mmusic@ietf.org Cc: Esteban Valverde (jovalver) <jovalver@cisco.com> Subject: RE: Signaling Additional SRTP Context information via SDP - draft-davis-mmusic-srtp-assurance Hi Kyzer, ... >Q.3 is two questions so I will address both: >A: The answer is value=unknown or no value at all are the same in the grand scheme. >The main difference is that I wanted to ensure an application had a way to explicitly call out that the value was unknown to them. >I could expand the text for one scenario that comes to mind which is: perhaps there was a scenario where it was known, then later >it became unknown and the app would like explicitly to state that as such and force a fallback to the default behavior. Would you not achieve the same thing by sending a new attribute without the value that has become unknown? Regards, Christer -----Original Message----- From: Christer Holmberg <mailto:christer.holmberg=40ericsson.com@dmarc.ietf.org> Sent: Tuesday, October 10, 2023 10:28 AM To: Kyzer Davis (kydavis) <mailto:kydavis@cisco.com>; mailto:mmusic@ietf.org Cc: Esteban Valverde (jovalver) <mailto:jovalver@cisco.com> Subject: RE: Signaling Additional SRTP Context information via SDP - draft-davis-mmusic-srtp-assurance Hi, A few questions, more related to the SDP usage than then mechanism itself. --- Q1: Section 3.1 says: srtp-context = srtp-attr srtp-tag [srtp-ssrc";"] [srtp-roc";"] [srtp-seq";"] [srtp-ext";"] I don’t think this is what you want, because you would have to add “;” also after the last field. Instead, you probably want something like: srtp-context = srtp-attr srtp-tag [srtp-param *(“;” srtp-param)] srtp-param = srtp-roc / srtp-seq / srtp-ext --- Q2: Section 3.1 says: srtp-ext = 1*VCHAR "=" (1*VCHAR / "unknown") ... VCHAR = %x21-7E I don't think you want to allow ";" (%x3B), because then one may not know whether it is part of the srtp-ext value or a separator between values. --- Q3: Section 3.1 says: “The value of "unknown" MAY be used in place of any of the fields to indicate default behavior SHOULD be utilized by the receiving application” How is that different from when the field is not included to begin with? Where are the default behaviors for the different fields defined? --- Q4: Section 3.1 says: "The tag for an SRTP Context attribute MUST follow the peer SDP Security a=crypto tag for a given media stream (m=)." It is unclear what "follow the tag" means. I assume you want to say that the SRTP Contect attribute MUST use the same tag value as the crypto attribute it is associated with? --- Regards, Christer From: mmusic <mailto:mmusic-bounces@ietf.org> On Behalf Of Kyzer Davis (kydavis) Sent: Monday, 9 October 2023 23.45 To: mailto:mmusic@ietf.org Cc: Esteban Valverde (jovalver) <mailto:jovalver@cisco.com> Subject: Re: [MMUSIC] Signaling Additional SRTP Context information via SDP - draft-davis-mmusic-srtp-assurance Group, I have posted draft 01 which covers the items from my previous email. Name: draft-davis-mmusic-srtp-assurance Revision: 01 Title: Signaling Additional SRTP Context information via SDP Date: 2023-10-09 Group: Individual Submission Pages: 21 URL: https://www.ietf.org/archive/id/draft-davis-mmusic-srtp-assurance-01.txt Status: https://datatracker.ietf.org/doc/draft-davis-mmusic-srtp-assurance/ HTML: https://www.ietf.org/archive/id/draft-davis-mmusic-srtp-assurance-01.html HTMLized: https://datatracker.ietf.org/doc/html/draft-davis-mmusic-srtp-assurance Diff: https://author-tools.ietf.org/iddiff?url2=draft-davis-mmusic-srtp-assurance-01 Thanks, From: mmusic <mailto:mmusic-bounces@ietf.org> On Behalf Of Kyzer Davis (kydavis) Sent: Thursday, August 10, 2023 11:30 AM To: mailto:mmusic@ietf.org Cc: Esteban Valverde (jovalver) <mailto:jovalver@cisco.com> Subject: [MMUSIC] Signaling Additional SRTP Context information via SDP - draft-davis-mmusic-srtp-assurance Hello all, I presented draft-davis-valverde-srtp-assurance-00 at Dispatch and the outcome was to dispatch to MMUSIC WG. I have re-submitted draft-davis-valverde-srtp-assurance-00 as draft-davis-mmusic-srtp-assurance-00 with no changes. To view that session and/slides see below: - https://youtu.be/KT3mMX9CMdA?t=3113 - https://datatracker.ietf.org/meeting/117/materials/slides-117-dispatch-sdp-security-assurance-for-secure-real-time-transport-protocol-srtp - A quick slide note, before the dispatch session I was working on a draft-01 which leveraged Solution A in these slides while draft-00 uses Solution B. - Jonathan Lennox brought up a good point after the session which favors solution B: - Paraphrasing: "We know how implementations will handle unknown SDP attributes; we do not know well how well how implementations will handle unknown SDP Security Session Parameters" - I dug into this a bit more and tend to agree. So draft-01 now continues to use solution B (a=srtpctx) new SDP Attribute to convey the required SRTP Context information alongside a=crypto. - I have a full write-up on GitHub with far more details: https://github.com/kyzer-davis/srtp-assurance-rfc-draft/issues/5 In addition, some other draft-01 actions items that were brought up in chat, at the mic or in person 1:1: - "Why this can't be a RTP Header Extension" from Richard Barnes. (https://github.com/kyzer-davis/srtp-assurance-rfc-draft/issues/11) - "Discuss sending some update when ROC updates" from Jonathan Rosenberg. (https://github.com/kyzer-davis/srtp-assurance-rfc-draft/issues/10) - Already text in the draft around this; which covers "99.9% of scenarios". - "Method to Convey Multiple SSRCs for a given stream" from various (https://github.com/kyzer-davis/srtp-assurance-rfc-draft/issues/1) - Two solutions proposed in the GitHub issue - A statement Cullen Jennings made about focusing on the problem statements. - I want to re-write the problem sections like RFC7744 where each problem in a scenario is cited as Ux.y and then discussed (Section 2.1.1 and 2.1.2) - I took a stab at a rough draft of this in "Discuss why SEQ is signaled in the SDP" via (https://github.com/kyzer-davis/srtp-assurance-rfc-draft/issues/9) - Overall item is in https://github.com/kyzer-davis/srtp-assurance-rfc-draft/issues/13 Lastly, the following items are already merged into draft-01 over on GitHub: - Change contact name from IESG to IETF in IANA Considerations #2 - Discuss RFC4568 "Late Joiner" in problem statement: #3 - Split Serial forking scenario into its own section #4 - Add MIKEY considerations to Protocol Design section #6 - Change doc title #7 (new title: "Signaling Additional SRTP Context information via SDP") - Add SEQ abbreviation earlier #8 Thanks, --- Kyzer Davis
- [MMUSIC] Signaling Additional SRTP Context inform… Kyzer Davis (kydavis)
- Re: [MMUSIC] Signaling Additional SRTP Context in… Kyzer Davis (kydavis)
- Re: [MMUSIC] Signaling Additional SRTP Context in… Christer Holmberg
- Re: [MMUSIC] Signaling Additional SRTP Context in… Kyzer Davis (kydavis)
- Re: [MMUSIC] Signaling Additional SRTP Context in… Kyzer Davis (kydavis)
- Re: [MMUSIC] Signaling Additional SRTP Context in… Christer Holmberg
- Re: [MMUSIC] Signaling Additional SRTP Context in… Kyzer Davis (kydavis)
- Re: [MMUSIC] Signaling Additional SRTP Context in… Kyzer Davis (kydavis)