Reviewer: Ralph Droms
Review result: Ready
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 wait for direction from your
document shepherd or AD before posting a new version
Reviewer: Ralph Droms
Review result: Ready
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
Reviewer: Ralph Droms
Review result: Ready with Nits
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
Reviewer: Ralph Droms
Review result: Ready
Document: draft-ietf-sidr-origin-validation-signaling-10
Reviewer: Ralph Droms
Review Date: 2016-12-10
IETF LC End Date: 2016-12-07
IESG Telechat date: 2016-12-15
Summary: This draft is ready for publication as a Proposed Standard
RFC
Note: My review
before posting a new
version of the draft.
For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Document: draft-ietf-stox-7248bis-13
Reviewer: Ralph Droms
Review Date: 2016-11-01
IETF LC End Date: 2016-10-06
IESG Telechat date: 2016-11-03
S
information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Document: draft-ietf-stox-7248bis-11
Reviewer: Ralph Droms
Review Date: 2016-11-01
IETF LC End Date: 2016-10-06
IESG Telechat date: 2016-11-03
Summary: This draft is ready for publication as a Pr
at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Document: draft-ietf-stir-certificates-10
Reviewer: Ralph Droms
Review Date: 2016-11-01
IETF LC End Date: 2016-11-01
IESG Telechat date: N/A
Summary: This draft is ready for publication as a Proposed Standard RFC.
Major issues
at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Document: draft-ietf-stox-7248bis-12
Reviewer: Ralph Droms
Review Date: 2016-10-21
IETF LC End Date: 2016-10-06
IESG Telechat date: 2016-11-03
Summary: Ready for publication as a Proposed Standard
I apologize for the late subm
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 wait for direction from your document shepherd or AD before
posting a new version of the draft. For more information,
RI just completed a quick review of draft-ietf-tram-turn-server-discovery-08.
The DNS Service Discovery section is much improved. I have a couple of
comments on the revised text:
I suggest adding a reference to the IANa "Service Name and Transport Protocol
Port Number Registry",
gt;
> Hi Ralph,
>
> Thanks for the review. Please see inline.
>
>> -----Original Message-
>> From: Ralph Droms [mailto:rdroms.i...@gmail.com
>> <mailto:rdroms.i...@gmail.com>]
>> Sent: Wednesday, August 10, 2016 2:58 AM
>> To: Review Area gen-ar
at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Document: draft-ietf-tram-turn-server-discovery-08
Reviewer: Ralph Droms
Review Date: 2016-08-09
IETF LC End Date: 2016-08-11
IESG Telechat date: unknown
Summary:
This draft is on the right track but has open issues, des
> On Jul 12, 2016, at 7:41 AM 7/12/16, Christer Holmberg
> wrote:
>
> Hi Ralph,
>
> Thanks for your comments! Please see inline.
>
> Minor issues:
>
> > I had some difficulty unraveling the relationship among the text in section
> > 3.3.2, 3.3.3, 4 and RFC
I am the assigned Gen-ART reviewer for this draft. The General AreaReview Team (Gen-ART) reviews all IETF documents being processedby the IESG for the IETF Chair. Please treat these comments justlike any other last call comments.For more information, please see the FAQ at.Document:
ttp://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>>.
Document: draft-ietf-idr-ix-bgp-route-server-10
Reviewer: Ralph Droms
Review Date: 2016-06-08
IETF LC End Date: ?
IESG Telechat date: 2016-06-16
Summary: This draft is ready for
> On May 18, 2016, at 9:29 PM 5/18/16, Jari Arkko wrote:
>
> Thanks for your review, Ralph!
You're welcome. I'm glad to hear you found the review valuable.
Responses in line...
>
> I do think some of the points you raised need to be addressed. Inline:
>
>>
>> #
ttp://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Document: draft-ietf-aqm-eval-guidelines-11
Reviewer: Ralph Droms
Review Date: 2016-04-28
IETF LC End Date: 2016-05-04
IESG Telechat date: 2016-05-19
Summary: This draft is on the right track but has open issues, described in the
review.
In gene
ttp://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>>.
Document: draft-ietf-lager-specification-11
Reviewer: Ralph Droms
Review Date: 2016-04-19
IETF LC End Date: 2016-04-11
IESG Telechat date: (if known) 2016-04-21
Summary: This dr
see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>>.
Document: draft-sparks-genarea-mailarch-improvements-02
Reviewer: Ralph Droms
Review Date: 2016-03-09
IETF LC End Date: 2016-02-18
IESG Telechat dat
ttp://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>>.
Document: draft-ietf-netmod-yang-json-08
Reviewer: Ralph Droms
Review Date: 2016-03-10
IETF LC End Date: 2016-03-10
IESG Telechat date: (if known)
Summary: This draft is ready for
Confirming that rev -15 addresses my Gen-ART review comments...
- Ralph
> On Dec 16, 2015, at 11:19 AM 12/16/15, Ralph Droms (rdroms)
> <rdr...@cisco.com> wrote:
>
>
>> On Dec 16, 2015, at 10:47 AM 12/16/15, Alexey Melnikov
>> <alexey.melni...@isode.com>
> On Dec 7, 2015, at 1:31 PM 12/7/15, Stephane Bortzmeyer <bortzme...@nic.fr>
> wrote:
>
> On Tue, Dec 01, 2015 at 01:55:46PM +0000,
> Ralph Droms (rdroms) <rdr...@cisco.com> wrote
> a message of 128 lines which said:
>
>> Would you consider adding a
mention below appear in rev -15?
- Ralph
>
> On 09/12/2015 20:47, Ralph Droms (rdroms) wrote:
>> Nits/editorial comments:
>>
>> Nicely written, very clear document.
> Thank you.
>> idnits reports some lines too long and an unused reference.
> I fixed the re
ttp://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Document: draft-ietf-httpauth-scram-auth-14
Reviewer: Ralph Droms
Review Date: 2015-13-9
IETF LC End Date: 2015-12-16
IESG Telechat date: (if known)
Summary: This draft is ready for publication as an Experimental RFC.
Major issues: None.
Minor
> On Nov 26, 2015, at 7:41 AM 11/26/15, Stephane Bortzmeyer <bortzme...@nic.fr>
> wrote:
>
> On Fri, Nov 20, 2015 at 04:22:21PM +0000,
> Ralph Droms (rdroms) <rdr...@cisco.com> wrote
> a message of 97 lines which said:
>
>> I am the assigned Gen-ART
> On Nov 23, 2015, at 9:01 AM 11/23/15, Tim Wicinski <tjw.i...@gmail.com> wrote:
>
> Ralph
>
> Thanks for the detailed review. Commeinline
>
> On 11/20/15 11:22 AM, Ralph Droms (rdroms) wrote:
>>
>> I am the assigned Gen-ART reviewer for
>&g
cument: draft-ietf-dnsop-qname-minimisation-07
Reviewer: Ralph Droms
Review Date: 2015-11-20
IETF LC End Date: 2015-11-23
IESG Telechat date: unknown
Summary:
This draft is on the right track but has open issues, described in the review.
Major issues:
The document is well-written and easy to unde
cument: draft-ietf-dnsop-qname-minimisation-07
Reviewer: Ralph Droms
Review Date: 2015-11-20
IETF LC End Date: 2015-11-23
IESG Telechat date: unknown
Summary:
This draft is on the right track but has open issues, described in the review.
Major issues:
The document is well-written and easy to unde
Himanshu <hs...@ciena.com> wrote:
>
> Thanks Andy.
> He did re-send the email without MIME and I was able to read and reply.
>
> Thanks,
> Himanshu
>
> From: Andrew G. Malis [mailto:agma...@gmail.com]
> Sent: Monday, October 26, 2015 2:08 PM
> To: Shah, Himanshu
>
> Now with the draft..
>
> Thanks,
> Himanshu
>
>
> -Original Message-
> From: Shah, Himanshu
> Sent: Saturday, October 24, 2015 5:52 PM
> To: 'Ralph Droms (rdroms)'
> Cc: 'A. Jean Mahoney'; 'General Area Review Team';
> 'draft-ietf-pals-mpls-tp-mac-wd..
apologies for the inaccuracy.
- Ralph
> On Oct 22, 2015, at 11:31 AM 10/22/15, Shah, Himanshu <hs...@ciena.com> wrote:
>
> Aahh! Finally got it with content!!..
>
> Let me go through your email..
>
> Thanks,
> Himanshu
>
>
> -Original Message-
> From: Ra
MIME…
>
> Thanks,
> Himanshu
>
> From: Ralph Droms (rdroms) [mailto:rdr...@cisco.com]
> Sent: Thursday, October 22, 2015 11:20 AM
> To: Shah, Himanshu
> Cc: A. Jean Mahoney; General Area Review Team;
> draft-ietf-pals-mpls-tp-mac-wd@ietf.org; The IESG
> Subject: Re:
e are two implementations of this draft deployed in a
> Telco network
> in Asia.
Noted.
>
>
> Thanks,
> Himanshu
>
>
> -Original Message-
> From: Ralph Droms (rdroms) [mailto:rdr...@cisco.com]
> Sent: Wednesday, October 14, 2015 4:02 PM
> To: A. Jea
e are two implementations of this draft deployed in a
> Telco network
> in Asia.
Noted.
>
>
> Thanks,
> Himanshu
>
>
> -Original Message-
> From: Ralph Droms (rdroms) [mailto:rdr...@cisco.com]
> Sent: Wednesday, October 14, 2015 4:02 PM
> To: A. Jea
his draft deployed in a
> Telco network
> in Asia.
Noted.
>
>
> Thanks,
> Himanshu
>
>
> -Original Message-
> From: Ralph Droms (rdroms) [mailto:rdr...@cisco.com]
> Sent: Wednesday, October 14, 2015 4:02 PM
> To: A. Jean Mahoney; General Area Review
ttp://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Document: draft-ietf-pals-mpls-tp-mac-wd-02, "MAC Address Withdrawal over
Static Pseudowire"
Reviewer: Ralph Droms
Review Date: 2015-10-14
IETF LC End Date: 2015-10-19
IESG Telechat date: (if known) N/A
Summary:
This draft is on the rig
ttp://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
Document: draft-ietf-pals-mpls-tp-mac-wd-02, "MAC Address Withdrawal over
Static Pseudowire"
Reviewer: Ralph Droms
Review Date: 2015-10-14
IETF LC End Date: 2015-10-19
IESG Telechat date: (if known) N/A
Summary:
This draft is on the rig
Francis, Jari - thanks for your reviews. I will address those editorial issues
in the next revision of the draft.
- Ralph
On Jun 10, 2014, at 3:37 AM 6/10/14, Jari Arkko jari.ar...@ericsson.com wrote:
Thanks for your review. I have also reviewed the document.
Jari
On 02 Jun 2014, at
Dan - thanks for your review. Responses in line; edits will appear in the -04
rev.
- Ralph
On Aug 25, 2013, at 7:29 AM 8/25/13, Romascanu, Dan (Dan)
droma...@avaya.com wrote:
I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART,
please see the FAQ at
Dan - thanks for your review.
On Aug 25, 2013, at 7:29 AM, Romascanu, Dan (Dan) droma...@avaya.com wrote:
I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART,
please see the FAQ at
http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq.
Please resolve these
Thanks, Brian.
- Ralph
On Sep 17, 2010, at 6:09 AM 9/17/10, Brian E Carpenter wrote:
draft-arkko-townsley-coexistence-04-carpenter.txt
___
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art
Russ - I've added the RFC Editor comments. I expect we'll need
another rev before publication, which should incorporate those comments.
- Ralph
On Aug 19, 2009, at 4:58 PM 8/19/09, Russ Housley wrote:
Ralph:
Russ - would you be willing to clear your DISCUSS and capture Joel's
new issues
Russ - would you be willing to clear your DISCUSS and capture Joel's
new issues in a COMMENT?
- Ralph
On Jul 27, 2009, at 4:56 AM 7/27/09, Joel M. Halpern wrote:
This document is nearly ready for publication as an Informational RFC.
While my comments have been resolved, some minor issues
Ralph Droms rdr...@cisco.com wrote:
For example, would a host process
information received from a Starbucks network over its 802.11
interface differently from information received a home network over
the 802.11 interface?
It's even more fun than that. How do we reliably know that we
Ted - I think it's just as likely for the RG to get different
information from different interfaces (or different administrative
domains) as it is for a host to get get different information
directly. Traffic from the host, which is then forwarded by the RG to
one of more than one
s...@employees.org:
Excerpts from Ralph Droms on Fri, Apr 10, 2009 03:25:49PM -0400:
Scott raises an interesting point about identifying the source of
options when delivered to clients.
BTW, Scott - what is DHS?
Sorry, DHCP server
The usual case - almost the only case today
in, but does this or could this interact with
the options specified in RFC3046 in an unexpected way?
At 01:41 PM 4/11/2009, Ralph Droms wrote:
Scott - even knowing which interface which DHCP information came
from may not be enough for a device with multiple interfaces. Can
policies for merging
- or does the device need to differentiate
between Verizon Wireless and Starbucks if I'm away from home? Or
differentiate between my ATT femtocell and my home WiFi network?
- Ralph
On Apr 11, 2009, at 6:00 AM 4/11/09, Scott Brim wrote:
Excerpts from Ralph Droms on Fri, Apr 10, 2009 03:25:49PM
Yeah. I have to agree with James and Brian: in retrospect, the M/O bits are
useless and further discussion at this point is even more useless.
- Ralph
On 11/29/06 4:58 AM, Brian E Carpenter [EMAIL PROTECTED] wrote:
The MO bits were
defined long before we had DHCPv6 in place.
And they
Spencer - thanks for your review and helpful comments.
You've correctly understood the Length and Prefix-Length fields; I'll update
those definitions.
Regarding Reserved - Always set to zero: I'll check the definition of the
Framed-IPv6-Prefix in RFC 3162 to understand the common practice (if
Spencer - It turns out this draft has a *very* long history. It is intended
to document the use of some optinos that date back to a time when IANA
handed out options codes for DHCP options *before* the defining RFC was
published. The current process for assigning option codes is defined in RFC
51 matches
Mail list logo