Warren Kumari has entered the following ballot position for
draft-ietf-uta-smtp-tlsrpt-18: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to
> On Apr 16, 2018, at 1:58 PM, Warren Kumari wrote:
>
> I throw away the one that contains 'bar', fair enough, got it. What I don't
> understand is what a record would look like which is a single record (#2), but
> that contains multiple strings (#3). Can you provide an
On Mon, Apr 16, 2018 at 2:08 PM, Viktor Dukhovni wrote:
>
>
>> On Apr 16, 2018, at 1:58 PM, Warren Kumari wrote:
>>
>> I throw away the one that contains 'bar', fair enough, got it. What I don't
>> understand is what a record would look like which is a
Benjamin Kaduk has entered the following ballot position for
draft-ietf-uta-smtp-tlsrpt-18: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer
Hi Benjamin,
Thank you for your review comments!
Just a generic reply on one of them:
On 16/04/2018 16:22, Benjamin Kaduk wrote:
Section 3
o "v": This value MUST be equal to "TLSRPTv1".
How about something like "This document defines version 1; other
versions may be defined in later
Hi,
I response to Phillip Hallam-Baker's SecDir review, I propose to add the
following note to the document:
--
[[RFC Editor: if draft-ietf-dnsop-attrleaf gets published as an RFC
before this document,
please add the following text (as a new 6.X Section) to the
> On Apr 16, 2018, at 2:24 PM, Warren Kumari wrote:
>
>> Strings in TXT records have a single-octet length field. When returning a
>> longer
>> string, or when one wants to explicitly segment a TXT RDATA into multiple
>> strings
>> one returns:
>>
>>txt.example.