E_R_O_T_I_K___P_U_R_!!!

Hallo, 

endlich bin ich frei und total hemmungslos nur fuer dich.

Wir koennen miteinander reden oder du schaust mir einfach zu.

Alles was DU willst!!!!

Ich kann dir eine voellig neue Seite von mir zeigen.

Ich mach dir ein Angebot, das du unmoeglich ablehnen kannst,

wenn du nur ein bischen Spass haben willst,

Ich warte auf dich!!!!

http://isabel69.yeah.net

Deine Isabel 

ILI - TÉCNICAS PRACTICAS DE NEGOCIACIÓN

El Instituto Iberoamericano de Logistica, Transporte y Comercio
Internacional tiene el agrado de comunicar la realizacion de la quinta
edicion en 2002 del:

CURSO DE TÉCNICAS PRACTICAS DE NEGOCIACIÓN 
23 al 27 de septiembre de 18.00 hs. a 22.00 hs. 

¿COMO APRENDER A PREPARAR Y DESARROLLAR UNA NEGOCIACIÓN?
TODA NEGOCIACIÓN ES UNA TAREA PROFESIONAL Y FUENTE DE VENTAJA COMPETITIVA,
TANTO PARA EL NEGOCIADOR COMO PARA LA 
EMPRESA.

OBJETIVOS
* Aprender a preparar las negociaciones, y a definir los resultados.
* Aprender los principios y técnicas de negociación para crear las
habilidades que faciliten la resolución de conflictos, aprovechamiento de
oportunidades y toma 
de decisiones.
* Aprender a reconocer los diferentes ámbitos en los que se desarrolla una
negociación y que requieran realizar actividades aproximación y acuerdo.
* Aprender a planear paso a paso el proceso de negociación, fijar los
objetivos y evaluar las diferentes alternativas.
* Aprender los enfoques que se deben adoptar en el proceso de negociación
según los actores,  participantes, los asuntos en discusión y los efectos
finales.
* Aprender los factores o elementos de mayor relevancia del negociador y
los cambios de enfoque en el curso del proceso de negociar.
* Aprender las diferentes técnicas de negociación, sus ventajas y
desventajas y cuando adoptar unas u otras de acuerdo al ambiente y a los
involucrados en cada 

To: ietf-ssh as a Good Person

Dear ietf-ssh:

You may ask yourself
      >    How to make people like you and respect you
      >    How to win friends
      >    How to let your conduct help your health, work, job, career, relationships, spirit,  mind, well-being, ...
      >    How to make your life smoother and happier 
      >    How to do whatever you like without being unpleasant to other people 
      >    How to develop good conduct in your children or students 
      >    How to make the world peaceful and better

You can find all the answers to these questions, and much more, in this great handbook:

" Complete Conduct Principles for the 21st Century " by Dr. John Newton 

It is the best educational GIFT idea for children, friends, relatives, classmates, students, parents,
teachers, other educators, ..., particularly at this special time. 

BENEFITS to each individual reader: Many! -- such as for health, work, job, career, self-improvement,
education, relationships, spirit, mind, well-being, and much more -- almost all the areas that are
important to you in the 21st century. People around you will benefit, too. (Please see the preface of the
book for details.) 

EVERYONE may find this handbook useful and helpful, regardless of age (from children to oldsters),
occupation, rank, status, gender, religious beliefs, nationality, country, or region. 

If you are a parent or a teacher, you can learn how to develop good conduct in your children or students from
this handbook. Please advise your children or students to read the book. It will result in great benefits
for both you and them. 

Draft draft of coming sftp revision...

Hello everyone,

It seems like it has been a while since we
had a ruckus on the mailing list -- so I
thought I'd post a draft-draft of the
coming version of the sftp draft.

My hope is that we can go at least one round
of changes quick and then publish in a
couple of weeks.

The list of things I've noted that have changed 
is below.  (This list is also part of the
document.)  There may be things I've missed.

I think most of this has been talked about
on the mailing list and at least some sort
of loose consensus has been achieved.

I unilaterally added the new error codes
and the  reserved range of packet types
for use by extensions  -- so I'm soliciting
feedback on these.

Also, I included the 'newline' extension for
use in conjunction with the SSH_FXF_TEXT
file open flag semi-uni-laterally.  So again,
if you can't stand it, scream now.  I like it
because it means most servers won't actually
have to do anything to implement SSH_FXF_TEXT.

Re: Updated SECSH-WG core drafts

Argh, I mangled that last re-send.  Let me try that again.

					- Bill

Updated SECSH-WG core drafts

Attached are updated versions of the SECSH-WG four core drafts.

The only changes are the addition of an 'Intellectual Property' section and
the removal of the previous 'Trademark Issues' section.

Since all four documents were revised the references have been udpated
as well.

-- 
Darren J Moffat

Network Working Group                                          T. Ylonen
Internet-Draft                                                T. Kivinen
Expires: March 21, 2003                 SSH Communications Security Corp
                                                             M. Saarinen
                                                 University of Jyvaskyla
                                                                T. Rinne
                                                             S. Lehtinen
                                        SSH Communications Security Corp
                                                      September 20, 2002


                       SSH Protocol Architecture
                  draft-ietf-secsh-architecture-13.txt

Status of this Memo

Re: Draft draft of coming sftp revision...

Joseph Galbraith <galb-list <at> vandyke.com> wrote:
> It seems like it has been a while since we had a ruckus on the
> mailing list -- so I thought I'd post a draft-draft of the coming
> version of the sftp draft.

First things first: I _like_ the human-readable error message field
in SSH_FXP_STATUS. This is something that institutions I have
contact with have been complaining bitterly about for ages - one lot
refused to provide SFTP to their users _at all_ simply because it
was unable to report errors with the same richness as SCP. Even if
every other proposed change gets shouted down, KEEP THIS ONE!

>    o  Added 'newline' extension.
>    o  Added SSH_FXF_TEXT file open flag.

These seem like a half-decent 90% solution (covers Windows, Mac and
Unix with no difficulty), but I'm concerned about the other 10% 

For a start, if you consider text file issues to be only about
newline conventions, you thereby ignore other problems such as
character sets. If a server uses EBCDIC and a client doesn't, is it
really the expected behaviour of a text-mode file transfer that it
should yield an EBCDIC file at the client end or an ASCII file on
the server? I was vaguely under the impression that (say) FTP's idea
of a text-mode transfer was that character sets would get converted.
Granted that EBCDIC is a pretty extreme example, but if one system
uses ISO-8859-1 while another uses UTF-8, or (more subtly) if two
systems use UTF-8 with different default normalisation forms, this
might still be an issue.

Re: Draft draft of coming sftp revision...

> > It seems like it has been a while since we had a ruckus on the
> > mailing list -- so I thought I'd post a draft-draft of the coming
> > version of the sftp draft.
> 
> First things first: I _like_ the human-readable error message field
> in SSH_FXP_STATUS. This is something that institutions I have
> contact with have been complaining bitterly about for ages - one lot
> refused to provide SFTP to their users _at all_ simply because it
> was unable to report errors with the same richness as SCP. Even if
> every other proposed change gets shouted down, KEEP THIS ONE!

That one actually existed in version 3 of
the protocol, before I started editing 
the draft   But I was a big proponent
of it too.

> >    o  Added 'newline' extension.
> >    o  Added SSH_FXF_TEXT file open flag.
> 
> These seem like a half-decent 90% solution (covers Windows, Mac and
> Unix with no difficulty), but I'm concerned about the other 10% 
> 
> For a start, if you consider text file issues to be only about
> newline conventions, you thereby ignore other problems such as
> character sets. If a server uses EBCDIC and a client doesn't, is it
> really the expected behaviour of a text-mode file transfer that it
> should yield an EBCDIC file at the client end or an ASCII file on
> the server? I was vaguely under the impression that (say) FTP's idea
> of a text-mode transfer was that character sets would get converted.
> Granted that EBCDIC is a pretty extreme example, but if one system

Re: Draft draft of coming sftp revision...

Joseph Galbraith <galb-list <at> vandyke.com> wrote:
> I am not a FTP guru, but I just talked to our FTP guru, and he tells
> me that stock FTP, at least, doesn't do any charset translation.
> There might be an extension for it.

Oh, OK. Fair enough.

> [charset translation can be done with an extension]

That's fair enough too.

> Okay; that's fair.  My first inclination is to say that anything not
> matching the servers newline sequence exactly (either the default
> \r\n, or newline as specified by the server) SHOULD NOT be
> translated. In particular, if the newline convention is \r\n, and
> the client sees a lone \r or lone \n, it should simply write the
> data through without modification.
> 
> What do you think?

Yes, that seems as good as anything to me. Realistically the only
instances of this I can easily bring to mind are

 (a) text files being stored on the server in the client's format
     already, in which case this algorithm will preserve whichever
     of \r and \n was the client's line-ending character, so it will
     end up looking plausible.

 (b) DOS text files containing CRs for purposes of visual weirdness,
     in which case this algorithm will transfer them correctly to

RE: Draft draft of coming sftp revision...

In general, the changes look good.

Specific comments:
5.3 Size
	I think that it needs to state that this is the binary size, and
that the number of bytes provided when the file is read in TEXT mode may be
different (either larger or smaller).

6.6 Creating and Deleting Directories
	There seems to be a missing "path" between the sentence about
attributes and "specified the directory to be created."  Also note that an
error can be returned from an attempt to delete a directory if the user does
not have permission for that operation.  Note that some systems may allow
file creates and deletes in a directory, but not deletion of the actual
directory due to separation of write access and delete access on the
directory.

In implementing the SSH_FXF_TEXT VMS should be able to seek text files for
reads with a little bit of work, but seeking a text file for write would
probably return an error more often than not.  Writes to an existing text
file when opened in Append mode should not be a problem.