(Q47164227)

10 January 2018

J. Fenton

1 reference

10 January 2018

Internet Engineering Task Force

M. Delany

1 reference

10 January 2018

1 reference

10 January 2018

language of work or name

1 reference

10 January 2018

August 2009

1 reference

10 January 2018

21

1 reference

10 January 2018

full work available at URL

https://tools.ietf.org/html/rfc5617

file format

HyperText Markup Language

1 reference

10 January 2018

https://tools.ietf.org/rfc/rfc5617.txt

1 reference

10 January 2018

https://www.rfc-editor.org/rfc/rfc5617.txt

1 reference

10 January 2018

https://www.rfc-editor.org/pdfrfc/rfc5617.txt.pdf

file format

Portable Document Format

1 reference

10 January 2018

RFC 8553: DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names

1 reference

2 April 2019

RFC 1035: Domain names - implementation and specification

1 reference

7.1

RFC 2119: Key words for use in RFCs to Indicate Requirement Levels

16

1 reference

7.1

RFC 4033: DNS Security Introduction and Requirements

16

1 reference

7.1

RFC 4592: The Role of Wildcards in the Domain Name System

16

1 reference

7.1

RFC 4871: DomainKeys Identified Mail (DKIM) Signatures

16

1 reference

7.1

RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs

16

1 reference

7.1

RFC 5234: Augmented BNF for Syntax Specifications: ABNF

16

1 reference

7.1

RFC 5322: Internet Message Format

16

1 reference

7.1

RFC 5451: Message Header Field for Indicating Message Authentication Status

16

1 reference

7.1

RFC 4686: Analysis of Threats Motivating DomainKeys Identified Mail (DKIM)

16

has characteristic

informative reference

1 reference

RfC ID

5617

7.2

RFC 5016: Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol

16

has characteristic

informative reference

1 reference

RfC ID

5617

7.2

RFC 5321: Simple Mail Transfer Protocol

16

has characteristic

informative reference

1 reference

RfC ID

5617

7.2