SVG Tests
thomas.fossati@arm.com
Security None Internet-Draft This memo is for experimenting with SVG in the context of RFC production.
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 . 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 14 September 2020.
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 () 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.
Table of Contents
  • .  Introduction
    • .  Conventions used in this document
    • .  Tools
  • .  Draw
  • .  Build
  • .  Examples
    • .  Hello World
    • .  An Inlined Sequence Diagram
    • .  A Sourced Box and Arrows Diagram
  • .  IANA Considerations
  • .  Security Considerations
  • .  Acknowledgments
  • .  Normative References
  • Author's Address
Introduction This memo is for experimenting with SVG in the context of RFC production. This document assumes a kramdown-rfc2629 based editing flow.
Conventions used in this document 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 when, and only when, they appear in all capitals, as shown here.
Tools Install goat and svgcheck (Go and Python are obvious preconditions): Install kramdown-rfc2629 (at least 1.3.2): = 1.3.2' ]]>
Draw Two options:
  • Either inline your ASCII / UTF-8 art:
  • Or source from an external file:
Build To go from markdown to XML, HTML and TXT: The "prepped" file, draft-fossati-svg-test.prepped.xml, can now be submitted to the datatracker.
Examples
Hello World ! ` ` 0 0 , ) Y o
An Inlined Sequence Diagram e g i i r i i ) R q g S g t C n o i ~ w E e e E n i C d < s f n g ~ f t r d e h t t u O i d S a f t i r e [ . t o i u S c ( e t a D d n l e i i u r l e e z u e t u v v a e r ) o n r e e E e n ~ l G h n t t r i m c # c e a S n C i t r n t i t s n a [ g r ~ n ~ S ' o n r ~ > i a S n i s 1 a k c i t r t e c ( 2 a a a ] d h ~ ) i d T t I e t a a l r e t e O N s p e a i . r n > a i T e t i a u c a # # e d u a u t u t t A o d a e r C V t r R c n i t R C l r t o u h e e e u n u e i a e i A t o c c r y w g ~ A ( R f e i C m e t a S d c a ~ n e u T e a n d i c i l i e a e . A t n e e i S i i t e O ~ a t n C r d R - f c i r n A n A s G e < t f ] n w R s c T S e S t e t e ~ r k e u A ~ a i A g i A < G S [ o w S ~ t T v d n r R c > t t n t ] e s t C T a N u ~ s ~ c C i c e | | | | | | | | [ No identity ] | | | | [ validation ] | | | | | | | | CSR | | | | Signature | | | o------------------->| | | | Acknowledgement | | Order' | |<-------------------o | Signature | | | o------------------->| | | | Required | | | | Authorizations | | | |<-------------------o | | | Responses | | | | Signature | | | o------------------->| | | | | | | |<~~~~Validation~~~~>| | | | | | | | CSR | | | | Signature | | | o------------------->| | | | Acknowledgement | | | |<-------------------o | | | | |<~~Await issuance~->| |<~~Await issuance~~>| | | | (unauthenticated) GET STAR certificate | o------------------------------------------------>| | Certificate #1 | |<------------------------------------------------o | (unauthenticated) GET STAR certificate | o------------------------------------------------>| | Certificate #2 | |<------------------------------------------------o | [...] | | (unauthenticated) GET STAR certificate | o------------------------------------------------>| | Certificate #n | |<------------------------------------------------o ]]>
A Sourced Box and Arrows Diagram
STIR Delegation Flow A 1 l A C 6 e S R S 5 A P l i S 4 r T S 1 e H T A S l e 3 2 e T A P l s 7 c C R T v E T e M T A d e l R H T 2 R P S P d T c d i | SP1 | dele | dele | | | | | | srv | cli +-----. | | | '----+-'------' | | 4 | '------^--|---------' 3 | | | | | .----|-----. | | 5 | | .---+--. | | | | '--->| ACME | | | | | | | STAR | C | 1 | | | +------| A | | | | .--->| HTTP | | | 2 | | | '---+--' | | | | | '----|-----' | .------|--v---------. 6 | | | .-+----.------. | | 7 | | | STAR | +-----' | '-->| SP2 | dele | HTTP | | | | | cli | |<--------------' | '----+-'-+----' | '-------------------' ]]>
IANA Considerations No requests are made to IANA.
Security Considerations There are none.
Acknowledgments Yaron for pointing out the current limitations in the tooling and providing the workaround. Carsten for working the kramdown magic.
Normative References Key words for use in RFCs to Indicate Requirement Levels In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.
Author's Address
thomas.fossati@arm.com