[rfc-i] draft-iab-rfc-use-of-pdf-01

HANSEN, TONY L tony at att.com
Tue Feb 23 11:32:45 PST 2016


Thanks Russ. I've filed an issue to change the text regarding I-D signatures.

	Tony



On 2/23/16, 2:08 PM, "rfc-interest on behalf of Russ Housley" <rfc-interest-bounces at rfc-editor.org on behalf of housley at vigilsec.com> wrote:

>This document suggests that the embedded signature be used for RFCs.  I'm fine with that.
>
>I'm working on an I-D that replaces RFC 5485.  It will use the embedded signature for PDF.
>
>Russ
>
>
>On Feb 23, 2016, at 2:01 PM, Joe Hildebrand (jhildebr) wrote:
>
>> I think the question is whether they're signed inside the PDF doc, or after the doc is created in an external file like the ASCII files are.
>> 
>> If I recall correctly, we either decided we wanted all of the output formats signed the same way, or we decided that the XML was what needed to be signed, since the output formats might get re-rendered one day.
>> 
>> -- 
>> Joe Hildebrand
>> 
>> 
>> 
>> 
>> 
>> 
>> On 2/23/16, 11:45 AM, "rfc-interest on behalf of Russ Housley" <rfc-interest-bounces at rfc-editor.org on behalf of housley at vigilsec.com> wrote:
>> 
>>> draft-iab-rfc-use-of-pdf-01 says:
>>> 
>>> Recommendation: At this time, the authors see no need for Internet-
>>> Drafts to be signed with a PDF digital signature.
>>> 
>>> The IETF Secretariat currently signs all I-Ds.  See RFC 5485.
>>> 
>>> It seems to me that the decision to sign I-Ds should be left to the IESG and IETF Secretariat.  I suggest that this be removed from the document.
>>> 
>>> Russ


More information about the rfc-interest mailing list