IETF Logo Mail Archive

[Uri-review] Requesting approval for URI schemes net.msmq, net.tcp, net.pipe

Piyush Joshi <Piyush.Joshi@microsoft.com> Mon, 17 January 2011 04:35 UTC

Return-Path: <Piyush.Joshi@microsoft.com>
X-Original-To: uri-review@core3.amsl.com
Delivered-To: uri-review@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C8C9D28C0EB for <uri-review@core3.amsl.com>; Sun, 16 Jan 2011 20:35:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.398
X-Spam-Level:
X-Spam-Status: No, score=-9.398 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CR4wd3xLLWPv for <uri-review@core3.amsl.com>; Sun, 16 Jan 2011 20:35:46 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 6986728C0E3 for <uri-review@ietf.org>; Sun, 16 Jan 2011 20:35:46 -0800 (PST)
Received: from TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sun, 16 Jan 2011 20:38:19 -0800
Received: from TK5EX14MBXC129.redmond.corp.microsoft.com ([169.254.8.218]) by TK5EX14MLTC101.redmond.corp.microsoft.com ([157.54.79.178]) with mapi id 14.01.0255.003; Sun, 16 Jan 2011 20:38:19 -0800
From: Piyush Joshi <Piyush.Joshi@microsoft.com>
To: "uri-review@ietf.org" <uri-review@ietf.org>
Thread-Topic: Requesting approval for URI schemes net.msmq, net.tcp, net.pipe
Thread-Index: Acu1/4H6rruEZoPgQjycrFNY9K3I6Q==
Date: Mon, 17 Jan 2011 04:38:18 +0000
Message-ID: <A4099F38038C2B45878B611167FA3EFB0E4441F5@TK5EX14MBXC129.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.123.12]
Content-Type: multipart/alternative; boundary="_000_A4099F38038C2B45878B611167FA3EFB0E4441F5TK5EX14MBXC129r_"
MIME-Version: 1.0
X-Mailman-Approved-At: Sun, 16 Jan 2011 22:01:36 -0800
Cc: Kirill Gavrylyuk <kirillg@microsoft.com>
Subject: [Uri-review] Requesting approval for URI schemes net.msmq, net.tcp, net.pipe
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jan 2011 05:05:23 -0000

This is to request approval for the following URI schemes. Please find the information below, requested as per the template defined in RFC4395.  Please let me know if you have any additional questions.

URI scheme names

1)      net.msmq (to specify communication using .Net Message Framing protocol<http://msdn.microsoft.com/en-us/library/cc219293(PROT.10).aspx> over Microsoft Message Queuing)

2)      net.tcp (to specify communication using .Net Message Framing protocol<http://msdn.microsoft.com/en-us/library/cc219293(PROT.10).aspx> over TCP)

3)      net.pipe (to specify communication using .Net Message Framing protocol<http://msdn.microsoft.com/en-us/library/cc219293(PROT.10).aspx> over Microsoft Windows Named Pipe)

References
[MC-NMF]: .NET Message Framing Protocol Specification<http://msdn.microsoft.com/en-us/library/cc219293(PROT.10).aspx> describes the base .Net Message Framing Protocol.
[MS-NMFMB]: .NET Message Framing MSMQ Binding Protocol Specification<http://msdn.microsoft.com/en-us/library/ff469340(PROT.10).aspx> describes the .Net Message Framing Protocol binding to MSMQ protocol. (For details on net.msmq scheme)
[MS-NMFTB]: .NET Message Framing TCP Binding Protocol Specification<http://msdn.microsoft.com/en-us/library/ee941638.aspx>  describes the .Net Message Framing Protocol binding to TCP protocol. (For details on net.tcp scheme)

Status
Requesting 'Permanent' status

URI scheme syntax and semantics

*         For net.msmq - defined in 3.1.1.2 of [MS-NMFMB]

*         For net.tcp - defined in 3.1.1 of [MS-NMFTB]

*         For net.pipe - similar to net.tcp when the communication is using [MC-NMF] over Microsoft Windows Named Pipe.

Encoding considerations
      There are no special encoding considerations for these schemes.

Applications/protocols that use this URI scheme name
      These schemes are used for communication over .Net Message Framing Protocol [MC-NMF] in Microsoft Windows Communication Framework<http://msdn.microsoft.com/en-us/netframework/aa663324.aspx>

Interoperability considerations
      These schemes are used for communication over .Net Message Framing Protocol [MC-NMF] which is available for implementers under Microsoft Open Specification<http://www.microsoft.com/openspecifications/en/us/default.aspx>.

Security considerations
      There are no special security considerations mandated by the use of the aforementioned schemes.

Contact
      Piyush Joshi (piyushjo@microsoft.com<mailto:piyushjo@microsoft.com>), Microsoft Corporation
      Kirill Gavrylyuk (kirillg@microsoft.com<mailto:kirillg@microsoft.com> ), Microsoft Corporation

Author/Change controller
      NA (this is a request for 'Permanent' status)


Please let me know if you have any questions.

Thank you

-          Piyush

v2.23.0 | Report a Bug | By Email