Re: [homenet] drafts on github

[Daniel Migault]

Thank you Barbara for the setting! I can see the drafts on the git!

Yours,
Daniel

On Wed, Aug 8, 2018 at 4:15 PM, STARK, BARBARA H  wrote:

> I’ve now finished the repository for -dhc-options, too. I saw the commits
> from Tomek were very old.
>
> I think everything looks ok at https://github.com/ietf-homenet-wg
> ,
> and the tools seem to work.
>
> So I think that mainly just leaves setting up the editors and additional
> aotomations.
>
> Barbara
>
>
>
> for more information.
>
> Daniel: Thanks for doing this.
>
> Just to add more change (no that’s not really the reason – the reason is
> to formalize things with official Note Wells and integrated IETF tools and
> such), we have an official homenet-wg github site (
> https://github.com/ietf-homenet-wg
> ).
> I’ve put the front-end-naming-delegation draft there. I did just a little
> bit to the .mkd Daniel created to make it Linux compatible (get rid of
> annoying end-of-line characters), added and deleted spaces to make markdown
> happy, and I successfully made the IETF tools stop complaining. And changed
> the extension to .md. The only “real” thing I changed was the
> howard-dnsop-ip6rdns draft reference to ietf-dnsop-ip6rdns.
> kramdown-rfc2629 successfully creates a .xml file for this .md; and xml2rfc
> successfully creates .html and .txt from that .xml.
>
>
>
> Daniel, you should now have permission to do things to this draft? I need
> to add the other editors to the team – maybe if editors could unicast me
> with your github user names?
>
>
>
> Next is -dhc-options. I see Tomek has been doing things, so I don’t want
> to set up the repository for this one till I know I have the latest.
>
> Barbara
>
>
>
>
>
>
>
> *From:* homenet  *On Behalf Of *Daniel Migault
> *Sent:* Friday, August 03, 2018 6:02 PM
> *To:* homenet 
> *Subject:* [homenet] drafts on github
>
>
>
> Hi,
>
>
>
> To ease collaboration I have converted to mkd the following drafts
>
> https://github.com/mglt/ietf-homenet-hna
> 
>
> https://github.com/mglt/ietf-homenet-hna-dhcp
> 
>
>
>
> I suggest we focus on the front-end-naming architecture draft, and I will
> catch up comments I have not yet answered.
>
>
>
> During IETF102, I git that the draft was too long. I believe that is
> resulting from considering all feed backs and details. Though I believe
> these are important pieces, I agree that some of them could be better
> placed in an appendix. I would be happy to get what the WG wants to put in
> appendix as well  as how the WG expects to shorten the draft.
>
>
>
> Yours,
>
> Daniel
>
> ___
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>
>
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet

Re: [homenet] drafts on github

[STARK, BARBARA H]

I’ve now finished the repository for -dhc-options, too. I saw the commits from 
Tomek were very old.
I think everything looks ok at 
https://github.com/ietf-homenet-wg,
 and the tools seem to work.
So I think that mainly just leaves setting up the editors and additional 
aotomations.
Barbara

for more information.
Daniel: Thanks for doing this.
Just to add more change (no that’s not really the reason – the reason is to 
formalize things with official Note Wells and integrated IETF tools and such), 
we have an official homenet-wg github site 
(https://github.com/ietf-homenet-wg).
 I’ve put the front-end-naming-delegation draft there. I did just a little bit 
to the .mkd Daniel created to make it Linux compatible (get rid of annoying 
end-of-line characters), added and deleted spaces to make markdown happy, and I 
successfully made the IETF tools stop complaining. And changed the extension to 
.md. The only “real” thing I changed was the howard-dnsop-ip6rdns draft 
reference to ietf-dnsop-ip6rdns. kramdown-rfc2629 successfully creates a .xml 
file for this .md; and xml2rfc successfully creates .html and .txt from that 
.xml.

Daniel, you should now have permission to do things to this draft? I need to 
add the other editors to the team – maybe if editors could unicast me with your 
github user names?

Next is -dhc-options. I see Tomek has been doing things, so I don’t want to set 
up the repository for this one till I know I have the latest.
Barbara



From: homenet mailto:homenet-boun...@ietf.org>> On 
Behalf Of Daniel Migault
Sent: Friday, August 03, 2018 6:02 PM
To: homenet mailto:homenet@ietf.org>>
Subject: [homenet] drafts on github

Hi,

To ease collaboration I have converted to mkd the following drafts
https://github.com/mglt/ietf-homenet-hna
https://github.com/mglt/ietf-homenet-hna-dhcp

I suggest we focus on the front-end-naming architecture draft, and I will catch 
up comments I have not yet answered.

During IETF102, I git that the draft was too long. I believe that is resulting 
from considering all feed backs and details. Though I believe these are 
important pieces, I agree that some of them could be better placed in an 
appendix. I would be happy to get what the WG wants to put in appendix as well  
as how the WG expects to shorten the draft.

Yours,
Daniel
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet

Re: [homenet] drafts on github

[STARK, BARBARA H]

Daniel: Thanks for doing this.
Just to add more change (no that’s not really the reason – the reason is to 
formalize things with official Note Wells and integrated IETF tools and such), 
we have an official homenet-wg github site 
(https://github.com/ietf-homenet-wg). I’ve put the front-end-naming-delegation 
draft there. I did just a little bit to the .mkd Daniel created to make it 
Linux compatible (get rid of annoying end-of-line characters), added and 
deleted spaces to make markdown happy, and I successfully made the IETF tools 
stop complaining. And changed the extension to .md. The only “real” thing I 
changed was the howard-dnsop-ip6rdns draft reference to ietf-dnsop-ip6rdns. 
kramdown-rfc2629 successfully creates a .xml file for this .md; and xml2rfc 
successfully creates .html and .txt from that .xml.

Daniel, you should now have permission to do things to this draft? I need to 
add the other editors to the team – maybe if editors could unicast me with your 
github user names?

Next is -dhc-options. I see Tomek has been doing things, so I don’t want to set 
up the repository for this one till I know I have the latest.
Barbara



From: homenet  On Behalf Of Daniel Migault
Sent: Friday, August 03, 2018 6:02 PM
To: homenet 
Subject: [homenet] drafts on github

Hi,

To ease collaboration I have converted to mkd the following drafts
https://github.com/mglt/ietf-homenet-hna
https://github.com/mglt/ietf-homenet-hna-dhcp

I suggest we focus on the front-end-naming architecture draft, and I will catch 
up comments I have not yet answered.

During IETF102, I git that the draft was too long. I believe that is resulting 
from considering all feed backs and details. Though I believe these are 
important pieces, I agree that some of them could be better placed in an 
appendix. I would be happy to get what the WG wants to put in appendix as well  
as how the WG expects to shorten the draft.

Yours,
Daniel
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet