Re: [Gen-art] Gen-ART review of draft-ietf-ippm-6man-pdm-option: Minor and editorial

2017-03-06 Thread jouni.nospam
respected FreeBSD > developer to create a version of FreeBSD which has PDM in it. > > We need to know exactly what choices one has in the OS stack itself. > > Thanks, > > Nalini Elkins > Inside Products, Inc. > www.insidethestack.com > (831) 659-8360 > > > F

Re: [Gen-art] Gen-ART review of draft-ietf-ippm-6man-pdm-option: Minor and editorial

2017-03-05 Thread jouni.nospam
Hi, Thank you for the updates. I am fine with them. I still have one fundamental complaint. There is no discussion or definition of the message timestamp points. All this nanosecond or better accuracy, and the concern of truncation inaccuracy do not really matter if the message timestamp point

Re: [Gen-art] Gen-ART review of draft-ietf-ippm-6man-pdm-option: Server Time

2017-02-22 Thread jouni.nospam
Hi, I’ll have a review of the changes shortly. Just wanted to acknowledge I’ve seen this mail ;) Thanks, Jouni > On Feb 21, 2017, at 10:12 AM, nalini.elk...@insidethestack.com wrote: > > I don't know why this email keeps getting cut off! > > I am attaching my response in a text file

Re: [Gen-art] Review of draft-elie-nntp-tls-recommendations-01

2016-12-07 Thread jouni.nospam
Hi Julien, What you propose below is what I was thinking about. So yes, OK with that. Thanks, Jouni > On Dec 7, 2016, at 1:19 PM, Julien ÉLIE wrote: > > Hi Jouni, > > First of all, thanks for having taken time to review the document. > > >> I think this document is ready for public

Re: [Gen-art] gen-art review of draft-ietf-dprive-dnsodtls-12

2016-11-29 Thread jouni.nospam
Thanks. > On Nov 28, 2016, at 9:50 PM, Tirumaleswar Reddy (tireddy) > wrote: > > Thanks, Jouni. Updated draft. > > -Tiru > >> -Original Message- >> From: jouni.nospam [mailto:jouni.nos...@gmail.com] >> Sent: Monday, November 28, 2016 11:1

Re: [Gen-art] gen-art review of draft-ietf-dprive-dnsodtls-12

2016-11-28 Thread jouni.nospam
Hi, Sorry for being under the radar. See my comments below. > On Nov 18, 2016, at 8:40 AM, Tirumaleswar Reddy (tireddy) > wrote: > >> -Original Message- >> From: jouni.nospam [mailto:jouni.nos...@gmail.com] >> Sent: Thursday, November 17, 2016 3:33 PM &g

[Gen-art] gen-art review of draft-ietf-dprive-dnsodtls-12

2016-11-17 Thread jouni.nospam
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at

Re: [Gen-art] Gen-ATR review of draft-ietf-ccamp-ospf-availability-extension-07

2016-10-18 Thread jouni.nospam
o me. I know having a normative reference in draft-ietf-ccamp-ospf-availability-extension to a new work is a bit of pain but I guess there’s no harm as you were already fine publishing an extension without describing how to implement it in the first place. - Jouni > > BR > Dan

Re: [Gen-art] Gen-ATR review of draft-ietf-ccamp-ospf-availability-extension-07

2016-10-17 Thread jouni.nospam
SI. But since > the conclusion is to use another different document, other than this document > to explain the technology specific usage(including the SC/SCSI allocation), > it’s preferred not to include the such text in this document. > > BR, > Amy > -Original Message

Re: [Gen-art] Gen-ATR review of draft-ietf-ccamp-ospf-availability-extension-07

2016-10-17 Thread jouni.nospam
t; For example, for the SCSI which supports TLV(e.g., OTN/WSON), a new type code > is needed to make use of availability TLV. > For the SCSI who doesn’t support TLV(e.g., PSC), a new SC types is needed. > > BR, > Amy > > -Original Message- > From: jouni.nospam [ma

[Gen-art] Gen-ATR review of draft-ietf-ccamp-ospf-availability-extension-07

2016-10-16 Thread jouni.nospam
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at