﻿<?xml version='1.0' encoding='utf-8'?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<?rfc iprnotified="no" ?>
<?rfc strict="no" ?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" consensus="true" docName="draft-moskowitz-tesla-update-gnss-sbas-00"
	category="std" ipr="trust200902" obsoletes="" updates="rfc4082" submissionType="IETF"
	xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" version="3">

<front> <title abbrev="TESLA Update">TESLA Update for GNSS SBAS Authentication</title>
    <seriesInfo name="Internet-Draft" value="draft-moskowitz-tesla-update-gnss-sbas-00"/>
	<author fullname="Robert Moskowitz" initials="R" surname="Moskowitz" role='editor'>
    <organization>HTT Consulting</organization>
    <address>
      <postal> 
	    <street></street>
        <city>Oak Park</city>
        <region>MI</region>
        <code>48237</code>
        <country>USA</country>
      </postal>
      <email>rgm@labs.htt-consult.com</email>
	</address>
	</author>
<date year="2025" />
   <area>sec</area>
   <workgroup>TBD</workgroup>
    <keyword>RFC</keyword>
     <keyword>Request for Comments</keyword>
     <keyword>I-D</keyword>
     <keyword>Internet-Draft</keyword>
     <keyword>TESLA</keyword>
<abstract>
<t>
	This document updates TESLA <xref target="RFC4082"/> to current 
	cryptographic methods for use by the International Civil Aviation 
	Organization (ICAO) in their Global Navigation Satellite System 
	(GNSS) Satellite-based augmentation system (SBAS) authentication 
	protocol.  The TESLA updates are to align it with current best 
	practices.
</t>
</abstract>
</front>
<middle>   
<section numbered="true" toc="default"> <name>Introduction</name>
<t> 
	TESLA <xref target="RFC4082"/> (Timed Efficient Stream 
	Loss-Tolerant Authentication) uses the best practices for 
	cryptography when published in 2005.  This is quite dated, and any 
	modern use of TESLA needs to adjust to current algorithms and 
	methods.
</t>
<t>
	This document focuses on thhe TESLA design targeted by the 
	International Civil Aviation Organization (ICAO) in their Global 
	Navigation Satellite System (GNSS) Satellite-based augmentation 
	system (SBAS) authentication protocol.
</t>
<t>
	The SBAS authentication protocol is more than a modern TESLA 
	implementation.  It uses a very tightly designed PKI and the C509 
	certificate encoding <xref target="I-D.ietf-cose-cbor-encoded-cert" 
	format="default"/> to work within the very highly constrained SBAS 
	communication link.  The PKI is out-of-scope for this document and 
	is described elsewhere within ICAO.
</t>
<t>
	This document is very much a "work in progress", in that various 
	ICAO SBAS documents need to be excised for their technical updates 
	to TESLA.  For example, TESLA specifies using a message 
	authentication code (MAC) of all communicated data.  SBAS is using 
	HMAC <xref target="RFC2104"/> and KMAC <xref 
	target="DOI_10.6028_NIST.SP.800-185" format="default"/>.
</t>
<section anchor="About_SBAS" numbered="true" toc="default"> <name>SBAS use of TESLA</name>
<t>
	The updating of TESLA in SBAS Authentication is outlined in <xref 
	target="DOI_10.33012_navi.595" format="default"/>.  This document 
	is the public source of changes made to TESLA and some of the 
	justifications.
</t>
</section>
</section>
<section anchor="terms" numbered="true" toc="default"> <name>Terms and Definitions</name>
<section numbered="true" toc="default"> <name>Requirements Terminology</name>
	<t>
		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 
		NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", 
		"MAY", and "OPTIONAL" in this document are to be interpreted as 
		described in BCP 14 <xref target="RFC2119" /> <xref 
		target="RFC8174" /> when, and only when, they appear in all 
		capitals, as shown here.
	</t>
</section>
</section>
<section anchor="Updates" numbered="true" toc="default"> <name>Updates to TESLA</name>
<t>
	TBD - extracted from SBAS documents.
</t>
</section>
<section anchor="IANA" numbered="true" toc="default"> <name>IANA Considerations</name>
<t>
	TBD
</t>
</section>
<section anchor="security-considerations" numbered="true" toc="default"> <name>Security Considerations</name>
<t>
	TBD
</t>
</section>
</middle>
<back>
<displayreference target="I-D.ietf-cose-cbor-encoded-cert" to="C509-Certificates"/>
<displayreference target="DOI_10.6028_NIST.SP.800-185" to="NIST.SP.800-185"/>
<displayreference target="DOI_10.33012_navi.595" to="SBAS Authentication"/>
<references> <name>References</name>
<references title="Normative References">
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4082.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
</references>
<references title="Informative References">
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2104.xml"/>
	<xi:include href="https://bib.ietf.org/public/rfc/bibxml7/reference.DOI.10.6028/NIST.SP.800-185.xml"/>
	<xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-ietf-cose-cbor-encoded-cert.xml"/>
	<reference anchor="DOI_10.33012_navi.595"  target="https://navi.ion.org/content/70/3/navi.595">
		<front>
			<title>Authentication of Satellite-Based Augmentation Systems with Over-the-Air Rekeying Schemes</title>
			<author
				initials="T.W." surname="Walter" fullname="Todd Walter">
			<organization>Journal of the Institute of Navigation</organization></author>
		</front>
	</reference>
</references>
</references>
<section numbered="false" toc="default"> <name>Acknowledgments</name>
<t>
	This work is in conjunction with the ICAO SBAS Authention Study 
	Group members.  This includes, and is not limited to: Jed Dennis 
	(FAA Consultant), Abdel Youssouf (Eurocontrol), Timo Warns 
	(Airbus), Todd Walter (Stanford) and chair Mikaël Mabilleau 
	(Eurocontrol).
</t>
</section>
</back>
</rfc>
