Category: Technical

It has finally happened, the IETF is relieving the IESG Secretariat of one of her most recognized roles, the proccessing of new Internet Draft Documents. Very soon there will be an automated procedure for submitting new Internet Draft Documents to the IETF/IESG. For many years the standing procedure has been that an Internet Draft Document author would prepare their drafts and email them to the IESG Secretariat to make them publicly availible to the Internet as a whole, the first milestone on the road to becoming an RFC. The human element is very important to the heritage of the I-D system. Without human hands guiding these documents to their destination it is possible that a document will be submitted and no one will ever see it as it simply becomes part of the larger public repository. There is a level of anticipation that will no longer be present, as each draft is availible instantly. Years ago it was exciting to me to submit my I-D to the IESG a few weeks before an IETF meeting, watching and waiting for my document to appear with everyone elses in the list of new drafts to be considered.
The IESG secretariat will still recieve documents that have been determined to have errors, most documents will make their way to the draft repositories without ever beeing met by human eyes.
Announced in: RFC 4228

Movable Type is starting to bug me. I don’t have a consistent blogging pattern, some days I blog 5 times, sometimes i wait 2 weeks between posts, and I have to pick between a number of posts to leave on the main page (usually 5) or a number of days to leave up (usually 10), there is no way to do something more elaborate.
I would like to be able to have there to always be at least 5 entries on the main page, regardless of age, but if I have blogged 25 entries in the past 10 days, I want them to all be there.

After many strange looks and much bitching from people about my email structure, it has chaged. The someuser*@curtis.kularski.net stuff is in the past for my personal email. My organizational, public and automated email stuff will still run through the old schema. My personal contacts will now be given a new, single address to use for contacting me. If you are a human, don’t SPAM and I like you, contact me and you will be given my new email address for immediate use.

I am working on restoring my image system to my blog. It is at http://www.disturbingthoughts.net/gallery.
I will be backing this one up as to not lose it again through some deranged Movable Type plugin.

I have completed 2 template candidates for my blog, feedback is greatly apprechiated from my readers.
Candidate 1 – http://www.realmofcurtis.net/DT1
or
Candidate 2 – http://www.realmofcurtis.net/DT2.
or
Candidate 3 – http://www.realmofcurtis.net/DT3
These demos are created in much the same way as the actual blog is, so everything should be almost exact. I have been considering something like this for a while, but have just not cared much about it until now.

For any of you who tried to wake me from my smei-comatose sleep earlier: I am alive and breathing, there is no need to worry.

Do I use enough images on my blog or would more be better? In the past few weeks I have only used like 2 images, the one of the two cute guys kissing and the one of Grace Hopper, only one of which probably actually appealed to any number of my readers (although, they are probably in the majority of my readers).
Maybe I should include more images of things in my life and just overall make the blog more image based? Since the MovableType/Plugin upgrade problem I have been lacking the image portion of my blog and I haven’t bothered to restore it yet (and probably wont until i configure it to not be in the same folder as the blog). I want to have an image portion again as well as provide more photographic evidence of the fact that I am alive, but im just not entirely sure how to incorporate it all.
Comments to this entry would be helpful I think.

Anyone out there feel out of the loop? Maybe even shy? The IETF has the solution for you!
Today the RFC editor released RFC 4144 – “How to Gain Prominence and Influence in Standards Organizations”. The document reads like a college of business text book. While the document is sound, it has no technical merit for which to earn a place in the great document series. Postel’s law states “be conservative in what you send”, but DAMN! PEOPLE GET A LIFE! Jon Postel didn’t need this type of a document to get people involved, he was just friendly and outgoing, he made contact with the newcomers, where has the IETF’s spirit for welcoming the noobs gone? (if anyone replies ICANN, I will hurt them). It is very important to get involved in Internet standards organizations if you care about the path that this great network takes, but find your own way, a way that works for you, not the path the author of this draft took. Embrace the organizations for what they are, if you work hard and are friendly you will get far in any organization. One day you could be chatting up in IRC with the big guys about something, and the next day you could be developing their plugin delievery mechanism (yes, im still jelous about that :-P).
Joyce, Sandy, please, retract this document and hold it for 1 April 2006. (Yes, its really that bad).
If you wish to read this fine piece of work and pass your own judgement on whether or not it is suitable for the RFC series, please feel free to grab your free copy from servers of the hardworking people at the IETF/IESG and RFC Editor. http://ftp.rfc-editor.org/in-notes/rfc4144.txt.
< END RANT >

I think im going to try to start using less parenthesis and brakets in my blog entries, and use anchor tags instead to create sort of a keyword effect. I have attempted it in my previous blog entry. If you like it, comment that you do, if you hate it, comment that you do. I do my blog mostly for me, but I like for my audience to be able to benefit from it.

I haven’t had a chance to restore the images from the little problem with MovableType, so they still aren’t here, and I will be restoring the gallery soon as well. Please ignore broken images and broken links on this blog until I have restored both of these resources.