Greetings,
Dan, have you received feedback? Were you also hoping to present or just
gather feedback and present at a later IETF.
Best regards,
Kathleen
On Thu, Sep 22, 2022 at 1:12 PM Dan Wing wrote:
> Secdispatch, opsawg,
>
> Based on earlier comments from Paul Wouters and Tommy Pauly, Tiru a
Hi EKR,
I'll assume you're happy with the previous responses. These are all
new comments and have been responded to and addressed.
I requested that the updated version be posted pending approval.
Responses inline.
On Wed, Mar 14, 2018 at 8:36 PM, Eric Rescorla wrote:
> I have reviewed the new
Hello Christian,
Thank you again for your review of the draft and comments to further
improve it. The updates should appear in the next revision. inline
On Sun, Feb 25, 2018 at 11:51 PM, Christopher Morrow
wrote:
>
>
> On Sat, Feb 24, 2018 at 10:29 PM, Christian Huitema
> wrote:
>>
>> Kathlee
there isn't an alternate ballot procedure.
On Mon, Feb 26, 2018 at 1:22 PM, Eric Rescorla wrote:
> Thanks for the updated draft. Some responses below.
>
>
> On Mon, Feb 19, 2018 at 12:11 PM, Kathleen Moriarty
> wrote:
>>
>>
>> >
>> > DISCUSS
>>
Sorry, I wasn’t able to task switch to editing the document yesterday with
other work obligations.
Best,
Kathleen
Sent from my mobile device
> On Feb 28, 2018, at 9:45 AM, Eric Rescorla wrote:
>
>
>
>> On Tue, Feb 27, 2018 at 11:23 AM, Warren Kumari wrote:
>> On Mon, Feb 26, 2018 at 3:2
Hi Alissa,
I believe this is the last set of comments received that we had left
to respond. The next update that will come out shortly following this
message should address all comments and subsequent discussions
received to date.
On Thu, Feb 8, 2018 at 8:26 AM, Alissa Cooper wrote:
> Alissa Co
Hi Eric,
A quick update per the discussion on a TLS draft.
On Mon, Feb 19, 2018 at 3:11 PM, Kathleen Moriarty
wrote:
> Hi Eric,
>
> Thanks for your feedback, responses are inline.
>
> FYI - I posted another version, but expect at least one more iteration
> after this versi
Hi Eric,
Thanks for your feedback, responses are inline.
FYI - I posted another version, but expect at least one more iteration
after this version with additional comments and the ones we haven't
gotten to yet.
On Thu, Feb 8, 2018 at 12:04 AM, Eric Rescorla wrote:
> Eric Rescorla has entered th
Hi Adam,
Thanks again for your updates. Responses inline.
On Tue, Feb 13, 2018 at 6:26 PM, Adam Roach wrote:
> Responses inline; some text elided.
>
> On 2/9/18 8:22 AM, Kathleen Moria
On Tue, Feb 13, 2018 at 6:35 PM, Adam Roach wrote:
> On 2/9/18 4:31 PM, MORTON, ALFRED C (AL) wrote:
>>>
>>> -Original Message-
>>> From: Adam Roach [mailto:a...@nostrum.com]
>>> Sent: Friday, February 09, 2018 3:34 PM
>>> To: MORTON, A
>> On Feb 9, 2018, at 1:18 PM, Kathleen Moriarty
>> wrote:
>>
>> Hi Ben,
>>
>> Thanks again for the comments, responses and proposals are inline.
>>
>> On Wed, Feb 7, 2018 at 12:40 AM, Ben Campbell wrote:
>>> Ben Campbell has enter
Hi Alexey,
Thanks again for your comments. Responses inline.
On Thu, Feb 8, 2018 at 9:16 AM, Kathleen Moriarty
wrote:
> On Thu, Feb 8, 2018 at 8:53 AM, Alexey Melnikov
> wrote:
>> Alexey Melnikov has entered the following ballot position for
>> draft-mm-wg-effect-encryp
Hi Mirja,
Now back to your comments. Thanks again for your assistance with
recommendations to reshape section 2 and other sections.
On Fri, Feb 2, 2018 at 10:19 AM, Kathleen Moriarty
wrote:
> On Fri, Feb 2, 2018 at 9:30 AM, Mirja Kühlewind wrote:
>> Mirja Kühlewind has entered the
On Fri, Feb 9, 2018 at 5:31 PM, MORTON, ALFRED C (AL) wrote:
>> -Original Message-
>> From: Adam Roach [mailto:a...@nostrum.com]
>> Sent: Friday, February 09, 2018 3:34 PM
>> To: MORTON, ALFRED C (AL)
>> Cc: Kathleen Moriarty; The IESG; opsawg@ietf.org;
ment.
>
Your edits look great and improve the text further. We’ll get them in the next
revision.
Thank you!
Kathleen
> Thanks!
> Deborah
>
>
> -Original Message-
> From: iesg [mailto:iesg-boun...@ietf.org] On Behalf Of Kathleen Moriarty
> Sent: Friday, Februar
I just posted a new version based on the discussion prior to this and will
update according to any follow ups from this or other edits. The update only
includes the comments responded to so far, more to come.
Thank you,
Kathleen
Sent from my mobile device
> On Feb 9, 2018, at 3:34 PM, Adam R
Hi Ben,
Thanks again for the comments, responses and proposals are inline.
On Wed, Feb 7, 2018 at 12:40 AM, Ben Campbell wrote:
> Ben Campbell has entered the following ballot position for
> draft-mm-wg-effect-encrypt-17: No Objection
>
> When responding, please keep the subject line intact and
Hi Deborah,
On Wed, Feb 7, 2018 at 4:35 PM, Deborah Brungard wrote:
> Deborah Brungard has entered the following ballot position for
> draft-mm-wg-effect-encrypt-17: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC
Hi Adam,
Thanks for the additional comments. We'll discuss in line and make
updates as appropriate.
On Mon, Feb 5, 2018 at 8:00 PM, Adam Roach wrote:
> Adam Roach has entered the following ballot position for
> draft-mm-wg-effect-encrypt-17: No Objection
>
> When responding, please keep the sub
On Thu, Feb 8, 2018 at 8:53 AM, Alexey Melnikov wrote:
> Alexey Melnikov has entered the following ballot position for
> draft-mm-wg-effect-encrypt-17: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel fr
On Wed, Feb 7, 2018 at 11:04 PM, Ben Campbell wrote:
>
>
>> On Feb 7, 2018, at 9:08 PM, Spencer Dawkins at IETF
>> wrote:
>>
>> -2.2.1: Please expand "QUIC" and add a citation.
>>
>> QUIC started out as an acronym (and went through two or three variations),
>> but sometime during the chartering
Hi Ben,
Thanks for the detailed comments. We will fold them into a revision
after the telechat (as I have no time before). We have some editorial
ones from Ben that will be folded in as well. We were hesitant to
change anything that was not requested as we didn't want to leave the
document in a
On Fri, Feb 2, 2018 at 9:30 AM, Mirja Kühlewind wrote:
> Mirja Kühlewind has entered the following ballot position for
> draft-mm-wg-effect-encrypt-17: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel fr
ifferences between
> draft-13 and draft-15.
>
> I am commenting here on Kathleen's message, to check whether various points
> are addressed.
>
>
> On 1/5/2018 6:07 AM, Kathleen Moriarty wrote:
>
> Christian,
>
> Thanks for your review. I'll respond inli
feedback.
>
> Best,
>
> Ines.
>
> 2018-01-04 20:13 GMT+02:00 Kathleen Moriarty
> :
>>
>> Hello Ines,
>>
>> Thanks again for your review. Edits have been made in our working
>> version that we hope to post soon.
>>
>> On Mon, Dec 11, 2017
Hello James,
Thank you for your review and suggestions, responses are inline.
On Fri, Dec 8, 2017 at 1:53 PM, james woodyatt wrote:
> On Dec 4, 2017, at 08:23, Christian Huitema wrote:
>>
>> In section 2.3.3, Application Layer Gateways, I was wishing it would say
>> something about IPv6. But th
Christian,
Thanks for your review. I'll respond inline to make sure we hit each
point raised. The next version posted may not address your points,
but the subsequent update should and I expect to have that out soon.
On Fri, Dec 8, 2017 at 11:25 AM, Kathleen Moriarty
wrote:
> T
Hello Ines,
Thanks again for your review. Edits have been made in our working
version that we hope to post soon.
On Mon, Dec 11, 2017 at 9:27 PM, Kathleen Moriarty
wrote:
> Ines,
>
> Thank you very much for your review! We're working on the comments
> received and the nits
Ines,
Thank you very much for your review! We're working on the comments
received and the nits you found will be addressed and are much
appreciated.
Best regards,
Kathleen
On Mon, Dec 11, 2017 at 4:59 PM, Ines Robles
wrote:
> Reviewer: Ines Robles
> Review result: Ready
>
> RtgDir review: draf
Thank you, Christain and others for your reviews. Our running draft
has addressed most comments received by mid-IETF week. We are working
on the others. We also received some comments from Kyle Rose and
Brandon Williams and are working to address those as well.
We'll respond on list when we get
On Thu, Nov 30, 2017 at 11:50 AM, Joe Clarke wrote:
> On 11/29/17 11:21, Kathleen Moriarty wrote:
>>> To that end, it might be useful to specifically point out where vendors
>>> have a
>>> role to fill in some of these areas to allow for transit encryption while
>
Hello Joe,
First, thank you for your helpful review.
On Wed, Nov 29, 2017 at 10:31 AM, Joe Clarke wrote:
> Reviewer: Joe Clarke
> Review result: Has Nits
>
> I have been requested to review draft-mm-wg-effect-encrypt for the ops
> directorate. This document describes the effects of pervasive en
Sent from my mobile device
> On Nov 18, 2017, at 2:34 PM, MORTON, ALFRED C (AL) wrote:
>
> Thanks for your review, Meral,
> we’ll make these changes in -14.
Yes, thank you for your review, Meral!
Kathleen
>
> regards,
> Al
>
> From: Meral Shirazipour [mailto:meral.shirazip...@ericsson.c
e use of encryption is possible.
Kathleen
>
>
> >
> >
> > Best Regards
> > Zongpeng Du
> >
> > -Original Message-
> > From: OPSAWG [mailto:opsawg-boun...@ietf.org] On Behalf Of Kathleen
> Moriarty
> > Sent: Monday, October 24, 2016 12
Kathleen Moriarty has entered the following ballot position for
draft-ietf-opsawg-capwap-alt-tunnel-08: 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
nd align extensible solutions that will address the scenario. In
>> doing so this work can provide the foundations for the next scenario in the
>> next iteration since many of the operational processes have common
>> information needs.
>>
>> Does this help to clear up how the
Hello,
I also took the time to read the draft and it currently reads like a
scenario or an expanded use case draft, not a solution draft. Does
SACM need this or is there plans to merge it with solution work into
one draft? I could see the value in the latter, but I don't see how a
scenario draft
Hi,
Sent from my iPhone
> On Jun 23, 2015, at 2:32 AM, Randy Presuhn
> wrote:
>
> Hi -
>
>> From: "Black, David"
>> Sent: Jun 22, 2015 5:06 PM
>> To: Randy Presuhn , Kathleen Moriarty
>>
>> Cc: "draft-ietf-opsawg-vmm-mi
On Mon, Jun 22, 2015 at 4:18 PM, Randy Presuhn wrote:
> Hi -
>
> >From: Kathleen Moriarty
> >Sent: Jun 22, 2015 12:49 PM
> >To: Randy Presuhn
> >Cc: The IESG , "
> draft-ietf-opsawg-vmm-mib.sheph...@ietf.org" <
> draft-ietf-opsawg-vmm-
On Mon, Jun 22, 2015 at 4:04 PM, Randy Presuhn wrote:
> Hi -
>
> >From: Kathleen Moriarty
> >Sent: Jun 22, 2015 12:45 PM
> >To: Michael MacFaden
> >Cc: "draft-ietf-opsawg-vmm-mib.sheph...@ietf.org" <
> draft-ietf-opsawg-vmm-mib.sheph...@ietf.org>
Hi,
Sent from my iPhone
> On Jun 22, 2015, at 6:58 PM, Randy Presuhn
> wrote:
>
> Hi -
>
>> From: Kathleen Moriarty
>> Sent: Jun 22, 2015 4:57 AM
>> To: The IESG
>> Cc: draft-ietf-opsawg-vmm-mib.sheph...@ietf.org,
>> draft-ietf-opsawg-vmm
Hi Mike,
Sent from my iPhone
> On Jun 22, 2015, at 9:08 PM, Michael MacFaden wrote:
>
> Agree there should be some warning here. But if this text is intended for
> those who implement it
> (like me) then I'd prefer to make it clear as mud what the issue is:
>
> Any implementation of this MI
Kathleen Moriarty has entered the following ballot position for
draft-ietf-opsawg-vmm-mib-03: 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
Sent from my iPhone
> On May 14, 2015, at 9:47 AM, "Stephen Farrell"
> wrote:
>
> Stephen Farrell has entered the following ballot position for
> draft-ietf-opsawg-hmac-sha-2-usm-snmp-06: Yes
>
> When responding, please keep the subject line intact and reply to all
> email addresses included
Kathleen Moriarty has entered the following ballot position for
draft-ietf-opsawg-hmac-sha-2-usm-snmp-06: Yes
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
Anuj,
Thanks for adding in the additional text, I think it is helpful.
Best regards,
Kathleen
On Sun, Mar 1, 2015 at 1:16 PM, Sehgal, Anuj
wrote:
> Hi Kathleen,
>
> > On 24 Feb 2015, at 3:35 pm, Kathleen Moriarty <
> kathleen.moriarty.i...@gmail.com> wrote:
> >
anges as
> draft-ietf-opsawg-coman-probstate-reqs-05.txt.
>
>
>
> Cheers,
> Mehmet
>
>
>
> *From:* ext Kathleen Moriarty [mailto:kathleen.moriarty.i...@gmail.com]
> *Sent:* Thursday, February 26, 2015 9:14 PM
> *To:* Juergen Schoenwaelder; Kathleen Moriarty; The IESG;
Kathleen Moriarty has entered the following ballot position for
draft-ietf-opsawg-coman-probstate-reqs-05: 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
Kathleen Moriarty has entered the following ballot position for
draft-ietf-opsawg-coman-use-cases-05: 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
and properly protect any
>security credentials that may be stored on the device (e.g., by
>using hardware protection mechanisms).
>
Yes, that works for me in combination with the updates to the use case
draft. Please let me know when the updated draft has been posted.
Thank
2015 at 8:51 AM, Sehgal, Anuj
wrote:
> Hi,
>
> The following inline comments are an overview of the actions taken
> to resolve the issues raised by Kathleen and Ted.
>
> > On 19 Feb 2015, at 4:43 pm, ext Kathleen Moriarty <
> kathlee
Kathleen Moriarty has entered the following ballot position for
draft-ietf-opsawg-coman-probstate-reqs-04: 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
Kathleen Moriarty has entered the following ballot position for
draft-ietf-opsawg-coman-use-cases-04: 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
53 matches
Mail list logo