dail-up ISP login can't do W3C encoding.

Please help resolve this 'argument' :--

Chris Glur wrote:

> > The dialer & ppp setup assumes that "@" would not be a valid
> > char of the UserID nor Password strings for ISPs.
> >
> > So when an ISP allocates a UserID containing char "@" [which
> > is legitimate per rfc] the system breaks.
> >
>
> Peter wrote:
> In an earlier discussion here, Pieter Muller
> suggested that special characters such as
> "@" be encoded according to a W3C encoding.

No ! When the ISP is logging-in it doesn't know about 'W3C encoding'.
Until login & password stage is completed, ppp is not used.
So the 'fancy stuff' of W3C encoding is not possible.

JD wrote:
> This is a problem in Native Oberon. The system expects that the user
> ID will not contain an "@" charecter. Most of the time people don't
> have an "@" in their user ID because the "@" seperates the user ID
> from the email server. But some ISPs use the "@" in user names for
> PPP and the PPP RFC doesn't disallow this. The workaround for this
> is to "escape" the "@" charecter with "%40".

No !! Would you also try to 'escape' the "3" in the tone-dialling
with a %51 ?!
---------------
Am I wrong, or how else can I word it so that they understand ?

Thanks for any info, possibly emailed also to
easlab AT absamail . co . za

== Chris Glur.




not@top-post

not@top-post writes:
> Please help resolve this 'argument' :--

The argument looks a bit bizarre to me.

> No ! When the ISP is logging-in it doesn't know about 'W3C encoding'.
> Until login & password stage is completed, ppp is not used.
> So the 'fancy stuff' of W3C encoding is not possible.

I have no idea what that's about.

PPP does have authentication built into it, and it does involve what
is essentially a login. I cannot tell what that text above is talking
about, though.

W3C encoding has _nothing_ to do with PPP, unless some ISP has a
convention using it. Such conventions are entirely outside the
standards -- not prohibited by it, but not documented either.

> No !! Would you also try to 'escape' the "3" in the tone-dialling
> with a %51 ?!
> ---------------
> Am I wrong, or how else can I word it so that they understand ?

This is lacking so much context that I don't think anyone can give you
a good answer.

Why would W3C %XX encoding have anything to do with it? What does
Oberon have to do with PPP? What exactly are you trying to do? What
problem is it you're trying to solve?

There's a lot missing here.

--
James Carlson, IP Systems Group <(E-Mail Removed)>
Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677