RFC 7472 on Internet Printing Protocol (IPP) over HTTPS Transport Binding and the 'ipps' URI Scheme
rfc-editor@rfc-editor.org Wed, 04 March 2015 01:53 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 984F51A8A9C for <ietf-announce@ietfa.amsl.com>; Tue, 3 Mar 2015 17:53:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 8LJM05ooZ7LN for <ietf-announce@ietfa.amsl.com>; Tue, 3 Mar 2015 17:53:02 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3B1011A8A95 for <ietf-announce@ietf.org>; Tue, 3 Mar 2015 17:52:48 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B0ABB180204; Tue, 3 Mar 2015 17:52:00 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7472 on Internet Printing Protocol (IPP) over HTTPS Transport Binding and the 'ipps' URI Scheme
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150304015200.B0ABB180204@rfc-editor.org>
Date: Tue, 03 Mar 2015 17:52:00 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/cF_ArsptcduwSwmYkq_rJj7If-Y>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2015 01:53:08 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7472
Title: Internet Printing Protocol (IPP) over
HTTPS Transport Binding and the 'ipps'
URI Scheme
Author: I. McDonald, M. Sweet
Status: Standards Track
Stream: IETF
Date: March 2015
Mailbox: blueroofmusic@gmail.com,
msweet@apple.com
Pages: 19
Characters: 37666
Updates: RFC 2910, RFC 2911
I-D Tag: draft-mcdonald-ipps-uri-scheme-18.txt
URL: https://www.rfc-editor.org/info/rfc7472
This document defines the Internet Printing Protocol (IPP) over HTTPS
transport binding and the corresponding 'ipps' URI scheme, which is
used to designate the access to the network location of a secure IPP
print service or a network resource managed by such a service.
This document defines an alternate IPP transport binding to that
defined in the original IPP URL Scheme (RFC 3510), but this document
does not update or obsolete RFC 3510.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC