LLCPS
draft-urien-tls-llcp-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-07-12
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
TLS Working Group                                            P. Urien 
  Internet Draft                                      Telecom ParisTech 
  Intended status: Experimental                                         
                                                                        
                                                           July 13 2013 
  Expires: January 2014 
 
                                     LLCPS 
                           draft-urien-tls-llcp-02.txt 
    
    
Abstract 
    
   This document describes the implementation, named LLCPS, of the TLS 
   protocol over the NFC (Near Field Communication) LLCP (Logical Link 
   Control Protocol) layer. The NFC peer to peer (P2P) protocol may be 
   used by any application that needs communication between two devices 
   at very small distances (a few centimeters). LLCPS enforces a strong 
   security in NFC P2P exchanges, and may be deployed for many 
   services, in the Internet Of Things (IoT) ecosystem, such as 
   payments, access control or ticketing operations. Applications 
   secured by LLCPS are identified by the service name 
   "urn:nfc:sn:tls:x" where x is the application name. 
    
Requirements Language 
    
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 
   document are to be interpreted as described in RFC 2119. 
    
Status of this Memo 
    
   This Internet-Draft is submitted in full conformance with the 
   provisions of BCP 78 and BCP 79. 
    
   Internet-Drafts are working documents of the Internet Engineering 
   Task Force (IETF). Note that other groups may also distribute 
   working documents as Internet-Drafts. The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/. 
    
   Internet-Drafts are draft documents valid for a maximum of six 
   months and may be updated, replaced, or obsoleted by other documents 
   at any time. It is inappropriate to use Internet-Drafts as reference 
   material or to cite them other than as "work in progress." 
    
   This Internet-Draft will expire on January 2014. 
    
   . 

   Urien                     Expires January 2014            [Page 1] 


Copyright Notice 
    
   Copyright (c) 2013 IETF Trust and the persons identified as the 
   document authors. All rights reserved. 
    
   This document is subject to BCP 78 and the IETF Trust's Legal 
   Provisions Relating to IETF Documents 
   (http://trustee.ietf.org/license-info) in effect on the date of 
   publication of this document. Please review these documents 
   carefully, as they describe your rights and restrictions with 
   respect to this document. Code Components extracted from this 
   document must include Simplified BSD License text as described in 
   Section 4.e of the Trust Legal Provisions and are provided without 
   warranty as described in the Simplified BSD License. 
    
    

   Urien                     Expires January 2014             [page 2] 

 
                                     LLCPS                   July 2013 
 
Table of Contents 
    
   Abstract........................................................... 1 
   Requirements Language.............................................. 1 
   Status of this Memo................................................ 1 
   Copyright Notice................................................... 2 
   1 Overview......................................................... 5 
      1.1 About the NFC protocol...................................... 5 
      1.2 The LLCP layer.............................................. 7 
      1.3 LLCPS basic guidelines...................................... 9 
   2 TLS support over LLCP, Connection-oriented Transport............ 10 
      2.1 Peer To Peer Link Establishment............................ 10 
      2.3 Connection Process, the Initiator is Server, the Target is 
      Client......................................................... 13 
          2.3.1 Initiator side ...................................... 13 
          2.3.2 Target side ......................................... 14 
          2.3.3 Connection choreography ............................. 14 
      2.4 Connection Process, the Initiator is Client, the Target is 
      Server......................................................... 14 
          2.4.1 Initiator side ...................................... 14 
          2.4.2 Target side ......................................... 15 
          2.4.3 Connection choreography ............................. 15 
      2.5 Disconnection Process...................................... 15 
          2.5.1 Disconnection initiated by the Initiator ............ 15 
          2.5.2 Disconnection initiated by the Target ............... 15 
Show full document text