Use Cases for RATS
draft-chen-rats-usecase-01

Document Type Active Internet-Draft (individual)
Authors chenmeiling  , Li Su 
Last updated 2020-09-10
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
RATS                                                             M. Chen
Internet-Draft                                                    Li. Su
Intended status: Informational                              China Mobile
Expires: March 14, 2021                               September 10, 2020

                           Use Cases for RATS
                       draft-chen-rats-usecase-01

Abstract

   This document presents two three scenarios from the Internet Service
   Providers' perspective as an supplement use case of the RATS work
   group.  And make some discussions of access authentication,
   application authentication and trusted link.

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 https://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 March 14, 2021.

Copyright Notice

   Copyright (c) 2020 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
   (https://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.

Chen & Su                Expires March 14, 2021                 [Page 1]
Internet-Draft               RATS Use Cases               September 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Access authentication based on different method . . . . .   3
     3.2.  Application authentication based on different system  . .   4
     3.3.  Use case based on trusted routing . . . . . . . . . . . .   5
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Informative References  . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   At present, it is necessary to complete the authentication before
   accessing the operator's network to obtain the service.  RATS aimed
   at the solutions to provide interoperable way for domain-specific
   attestation mechanisms, within RATS relying party may not to maintain
   the authentication background, as an ISP what may be involved at the
   level of access authentication is preshared secret keys based
   authentication, the authentication based on PSK(Preshared secret
   keys) is different from identity-based authentication, such as
   IBC(Identity-Based Cryptograph).

   After access to the network, operators can also provide application
   layer authentication services for a variety of applications.  At
   present, there are many application layer authentication methods, it
   can be divided into certificate-based and non-certificate-based
   certification systems, so there are the following situations.  One
   application authenticated by certificate-based PKI system may request
   resource access to a server or service, but the server or service's
   authentication function is based on identity which is belong to non-
   certificate-based certification systems.  These are all possible
   future demand scenarios, also in the context of the RATS.  Due to
   limitation of resource, many companies are unable to operate their
   own certification and willing to rely on the result from operator to
   reduce their cost, and operator can provide authentication services.
   Multiple certification centers would be made due to different kinds
   of request from service and perspective of deployment, before
   obtaining a certification center's service, certification center need
   proof for identification, including software and hardware health
   information.  These certification centers are based on regions then
   there have manage barriers, how can clients from a certification
   center asstest themselves' identities to another certification
Show full document text