[VCARDDAV] Fwd: [rfc-dist] RFC 6869 on vCard KIND:device

Gonzalo Salgueiro <gsalguei@cisco.com> Sat, 09 February 2013 02:26 UTC

Return-Path: <gsalguei@cisco.com>
X-Original-To: vcarddav@ietfa.amsl.com
Delivered-To: vcarddav@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1C5221F8CA7 for <vcarddav@ietfa.amsl.com>; Fri, 8 Feb 2013 18:26:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.924
X-Spam-Level:
X-Spam-Status: No, score=-9.924 tagged_above=-999 required=5 tests=[AWL=-0.525, BAYES_00=-2.599, J_CHICKENPOX_46=0.6, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WVeTUBKAZewc for <vcarddav@ietfa.amsl.com>; Fri, 8 Feb 2013 18:26:38 -0800 (PST)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id 325AB21F8CA6 for <vcarddav@ietf.org>; Fri, 8 Feb 2013 18:26:38 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r192Qban020269 for <vcarddav@ietf.org>; Fri, 8 Feb 2013 21:26:37 -0500 (EST)
Received: from rtp-gsalguei-8918.cisco.com (rtp-gsalguei-8918.cisco.com [10.116.132.57]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r192Qbld002767 for <vcarddav@ietf.org>; Fri, 8 Feb 2013 21:26:37 -0500 (EST)
From: Gonzalo Salgueiro <gsalguei@cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Fri, 08 Feb 2013 21:26:35 -0500
References: <20130209014829.0F32EB1E008@rfc-editor.org>
To: CardDAV <vcarddav@ietf.org>
Message-Id: <89A564D3-2AA8-4807-9232-F69E54F05010@cisco.com>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Subject: [VCARDDAV] Fwd: [rfc-dist] RFC 6869 on vCard KIND:device
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vcarddav>
List-Post: <mailto:vcarddav@ietf.org>
List-Help: <mailto:vcarddav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 02:26:38 -0000

FYI

Begin forwarded message:

> From: rfc-editor@rfc-editor.org
> Subject: [rfc-dist] RFC 6869 on vCard KIND:device
> Date: February 8, 2013 8:48:29 PM EST
> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Cc: rfc-editor@rfc-editor.org
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>        RFC 6869
> 
>        Title:      vCard KIND:device 
>        Author:     G. Salgueiro, J. Clarke,
>                    P. Saint-Andre
>        Status:     Standards Track
>        Stream:     IETF
>        Date:       February 2013
>        Mailbox:    gsalguei@cisco.com, 
>                    jclarke@cisco.com, 
>                    psaintan@cisco.com
>        Pages:      9
>        Characters: 14648
>        Updates/Obsoletes/SeeAlso:   None
> 
>        I-D Tag:    draft-salgueiro-vcarddav-kind-device-07.txt
> 
>        URL:        http://www.rfc-editor.org/rfc/rfc6869.txt
> 
> This document defines a value of "device" for the vCard KIND property
> so that the vCard format can be used to represent computing devices
> such as appliances, computers, or network elements (e.g., a server,
> router, switch, printer, sensor, or phone).  [STANDARDS-TRACK]
> 
> 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 Internet
> Official Protocol Standards (STD 1) 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
>  http://www.ietf.org/mailman/listinfo/ietf-announce
>  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> 
> For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
> For downloading RFCs, see http://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
> 
> 
> _______________________________________________
> rfc-dist mailing list
> rfc-dist@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-dist
> http://www.rfc-editor.org
>