[plasma] Plasma transport and encoding

Dan Griffin <dan@jwsecure.com> Wed, 27 June 2012 20:12 UTC

Return-Path: <dan@jwsecure.com>
X-Original-To: plasma@ietfa.amsl.com
Delivered-To: plasma@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9083E11E80A5 for <plasma@ietfa.amsl.com>; Wed, 27 Jun 2012 13:12:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ezw-twkN9Xh for <plasma@ietfa.amsl.com>; Wed, 27 Jun 2012 13:12:50 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe001.messaging.microsoft.com [216.32.180.11]) by ietfa.amsl.com (Postfix) with ESMTP id 7F45211E808F for <plasma@ietf.org>; Wed, 27 Jun 2012 13:12:50 -0700 (PDT)
Received: from mail172-va3-R.bigfish.com (10.7.14.252) by VA3EHSOBE013.bigfish.com (10.7.40.63) with Microsoft SMTP Server id 14.1.225.23; Wed, 27 Jun 2012 20:11:05 +0000
Received: from mail172-va3 (localhost [127.0.0.1]) by mail172-va3-R.bigfish.com (Postfix) with ESMTP id 4A88A1A034F for <plasma@ietf.org>; Wed, 27 Jun 2012 20:11:05 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.237.149; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0511HT004.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -2
X-BigFish: PS-2(zzc85fh4015I14ffIzz1202hzz8275bh8275dhz2fh2a8h668h839hd25hf0ah)
Received-SPF: pass (mail172-va3: domain of jwsecure.com designates 157.56.237.149 as permitted sender) client-ip=157.56.237.149; envelope-from=dan@jwsecure.com; helo=BY2PRD0511HT004.namprd05.prod.outlook.com ; .outlook.com ;
Received: from mail172-va3 (localhost.localdomain [127.0.0.1]) by mail172-va3 (MessageSwitch) id 1340827862411231_32481; Wed, 27 Jun 2012 20:11:02 +0000 (UTC)
Received: from VA3EHSMHS023.bigfish.com (unknown [10.7.14.245]) by mail172-va3.bigfish.com (Postfix) with ESMTP id 61240220048 for <plasma@ietf.org>; Wed, 27 Jun 2012 20:11:02 +0000 (UTC)
Received: from BY2PRD0511HT004.namprd05.prod.outlook.com (157.56.237.149) by VA3EHSMHS023.bigfish.com (10.7.99.33) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 27 Jun 2012 20:10:58 +0000
Received: from BY2PRD0511MB427.namprd05.prod.outlook.com ([169.254.2.160]) by BY2PRD0511HT004.namprd05.prod.outlook.com ([10.255.129.39]) with mapi id 14.16.0164.004; Wed, 27 Jun 2012 20:12:41 +0000
From: Dan Griffin <dan@jwsecure.com>
To: "plasma@ietf.org" <plasma@ietf.org>
Thread-Topic: Plasma transport and encoding
Thread-Index: Ac1Un6CkmtHhhI/JSlW75M5733VGgQ==
Date: Wed, 27 Jun 2012 20:12:40 +0000
Message-ID: <B66E1F139A0F29418103E63A6124AC1C09FDFB2E@BY2PRD0511MB427.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.160.196.25]
Content-Type: multipart/alternative; boundary="_000_B66E1F139A0F29418103E63A6124AC1C09FDFB2EBY2PRD0511MB427_"
MIME-Version: 1.0
X-OriginatorOrg: jwsecure.com
Subject: [plasma] Plasma transport and encoding
X-BeenThere: plasma@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The PoLicy Augmented S/Mime \(plasma\) bof discussion list." <plasma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/plasma>, <mailto:plasma-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/plasma>
List-Post: <mailto:plasma@ietf.org>
List-Help: <mailto:plasma-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/plasma>, <mailto:plasma-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jun 2012 20:17:12 -0000

Hi all - we're implementing a proof of concept Plasma server using WCF in Microsoft .NET and we want to maximize the likelihood that our solution is interoperable. We see in section 4 of EPS TRUST that TLS 1.1 is a requirement, but questions such as transport and message encoding seem to have been left open. Are text-encoded SOAP 1.x messages over HTTP what's intended?

Thanks,
Dan